Linkinator Mcp
Crawl your site or docs for broken links through your agent before release instead of running linkinator only from the terminal.
Overview
io.github.JustinBeckwith/linkinator-mcp is a MCP server for the Ship phase that runs linkinator-based link checking for your agent over stdio.
What is this MCP server?
- Wraps the linkinator link checker as an MCP server (linkinator-mcp v0.2.5)
- stdio npm transport for Claude Code, Cursor, and generic MCP hosts
- Suites solo builders shipping landing pages, docs sites, and SaaS marketing URLs
- Focused scope: link health, not full Lighthouse or visual regression
- Repository: github.com/JustinBeckwith/linkinator-mcp
- Server version 0.2.5
- Transport: stdio
- npm identifier: linkinator-mcp
Community signal: 3 GitHub stars.
What problem does it solve?
Solo builders ship docs and marketing sites with dead links because crawling URLs is a separate terminal step agents cannot trigger.
Who is it for?
Builders preparing to ship or redeploy content-heavy sites who want MCP-driven broken-link reports inside Claude Code or Cursor.
Skip if: Teams that need full browser E2E, accessibility audits, or SEO keyword research without any link crawl.
What do I get? / Deliverables
After install, your agent can kick off linkinator scans and surface broken URLs in the same session where you fix content or routes.
- Agent-triggered linkinator crawls with broken-link findings
- Repeatable link QA without leaving the coding session
- Reports suitable for fixing routes and markdown hrefs before ship
Recommended MCP Servers
Journey fit
Ship is the right shelf because link validation is a pre-release quality gate—you catch 404s and bad redirects before users and search bots do. Testing fits automated URL checks across marketing pages, blogs, and app shells as part of ship-ready verification.
How it compares
Link crawl MCP wrapper around linkinator, not a Launch-phase SEO content optimizer or monitoring platform.
Common Questions / FAQ
Who is io.github.JustinBeckwith/linkinator-mcp for?
It is for developers and solo founders who want their AI assistant to run linkinator checks on sites and docs via MCP.
When should I use io.github.JustinBeckwith/linkinator-mcp?
Use it during Ship testing when you are validating hrefs on staging or production-bound URLs before release.
How do I add io.github.JustinBeckwith/linkinator-mcp to my agent?
Install linkinator-mcp from npm, add it as a stdio MCP server in Claude Code or Cursor, then invoke link-check tools against your target URLs.