crawlcove-mcp
OfficialSummary: An MCP server that crawls a site (or loads an existing crawl export) and answers SEO questions about it from real crawl data.
Crawl a site live (
crawl_site) — same-origin, breadth-first, robots.txt respected, default 50 / max 200 pages, optionalignoreRobots; result becomes the active dataset.Load a crawl from disk (
load_export) — Crawl Cove desktop JSON export or crawlcove-cli result, no page cap, more per-page data (depth, word count, content type) but no link graph.List SEO issues (
get_issues) — filter by type: broken-page, missing/long/duplicate title, missing/long meta description, missing/multiple H1, noindex, redirect-chain, missing-canonical (up to 500).Inspect a single page (
get_page) — status, title, meta description, H1 count, canonical, robots, redirect hops, broken links out.Find broken internal links (
list_broken_links) — source page → broken target pairs so you know what to fix (live crawl / CLI datasets only).List and filter pages (
list_pages) — by status code, indexability, or URL substring (up to 1000).Runs anywhere — any MCP client (Claude Desktop, Claude Code, Cursor) via
npxstraight from GitHub, nothing to install.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@crawlcove-mcp crawl https://example.com and list every SEO issue you find"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
crawlcove-mcp
An MCP server that gives Claude, Cursor, Claude Code and any other MCP client your site's SEO crawl data — ask "which pages are missing meta descriptions?", "what links to the 404s?", or "crawl staging and tell me what's wrong" and get answers from a real crawl, not a guess.
Setup
Requires Node 18+. Nothing to install: MCP clients run the server with npx straight from GitHub (the npm package is coming).
Claude Desktop — claude_desktop_config.json:
{
"mcpServers": {
"crawlcove": {
"command": "npx",
"args": ["-y", "github:CrawlCove/seo-mcp-server"]
}
}
}Claude Code:
claude mcp add crawlcove -- npx -y github:CrawlCove/seo-mcp-serverCursor — .cursor/mcp.json in your project (or the global one):
{
"mcpServers": {
"crawlcove": {
"command": "npx",
"args": ["-y", "github:CrawlCove/seo-mcp-server"]
}
}
}The first start takes a few seconds while npx fetches the package; after that it is cached.
Related MCP server: Screaming Frog MCP Server
Tools
Tool | What it does |
| Live crawl of a site (same-origin, breadth-first, robots.txt respected), up to 200 pages. Becomes the active dataset. |
| Load a Crawl Cove desktop app JSON export (Reports → Export → JSON) or a |
| The SEO issues in the active dataset. Types: |
| Everything recorded about one URL: status, title, meta description, H1 count, canonical, robots, redirect hops, broken links out. |
| Broken internal links as source page → broken target, so you know which page to fix. |
| Pages with status and title, filtered. |
Things to ask once it is connected:
"Crawl https://staging.example.com and list every issue."
"Which pages are missing meta descriptions? Draft one for each."
"What links to the 404s?"
"Load ~/Downloads/crawl-export.json and show me the noindex pages."
Where the data comes from
Live crawls use the same crawler as crawlcove-cli: same-origin links only, robots.txt honoured (a
User-agent: crawlcove-cligroup is respected over*), a hard cap of 200 pages so an assistant cannot accidentally hammer a site. Broken-link sources are available because the crawler keeps the link graph.Desktop exports follow crawlcove-export-spec and carry more per page (depth, word count, content type, X-Robots-Tag-aware indexability) with no page cap — but no link graph, so
list_broken_linkslists the broken pages and points you at the app for inlinks.
Works with CrawlCove
This server is the assistant-facing half of Crawl Cove, a desktop SEO crawler for Windows and Mac. For anything past 200 pages, for history over time, for Search Console data next to the crawl, or to fix findings in bulk, run the crawl in the desktop app and hand its export to load_export.
This repo has its own page on crawlcove.com: Crawl Cove MCP server.
Development
npm ci && npm run build && npm testdist/ is committed (it is what npx github:… runs); CI fails if it is stale. The server logic is in src/server.ts; the pure dataset layer (src/dataset.ts) has no MCP dependency and is exported for scripting.
Related tools
crawlcove-js —
crawlcove-export, a typed JavaScript/TypeScript library to load, query and convert Crawl Cove exports.crawlcove-sheets — Google Sheets add-on that turns a Crawl Cove export into an audit workbook (issues by type, pages by status, title/meta flags).
crawlcove-sf-import — convert a Screaming Frog export into the Crawl Cove export format, with a report of what carried over.
crawlcove-schema-validator — validate a page's JSON-LD against Google's required and recommended rich-result properties.
crawlcove-hreflang-checker — check a page's or a sitemap's hreflang tags: codes, self-reference, x-default and return tags.
crawlcove-cli — the command line crawler this server uses for live crawls.
crawlcove-action — the same checks as a GitHub Action on every PR.
crawlcove-export-spec — the JSON Schema for the desktop export
load_exportreads.crawl-cove-connector — WordPress plugin that applies Crawl Cove's approved fixes to Yoast, Rank Math, SEOPress or AIOSEO.
crawlcove-redirect-chain-checker — follow every hop of a URL’s redirects; flags chains, loops, HTTPS downgrades and meta refreshes.
crawlcove-sitemap-validator — validate an XML sitemap or sitemap index against the protocol and search-engine limits.
crawlcove-robots-txt-tester — lint a robots.txt and test which URLs each crawler may fetch, with the deciding line.
seo-chrome-extension — Chrome extension: on-page SEO check of the current tab plus AI answer visibility (which AI crawlers may read it, snippet blocks, llms.txt, extractability score).
License
MIT — see LICENSE.
Available Tools
6 toolscrawl_siteCrawl a siteA
Crawl a website live (same-origin, breadth-first, robots.txt respected) and make the result the active dataset for the other tools. Capped at 200 pages; for a full-site audit with history and Search Console data, use the Crawl Cove desktop app and load its export with load_export.
Inputs: url (required), maxPages, ignoreRobots.
get_issuesList SEO issuesA
List the SEO issues found in the active dataset, optionally one type only. Types: broken-page (The page returned a 4xx/5xx status or could not be fetched); missing-title (No ); long-title ( longer than 60 characters (may be truncated in search results)); duplicate-title (The same is used on more than one page); missing-meta-description (No ); long-meta-description (Meta description longer than 160 characters); missing-h1 (No on a 200 HTML page); multiple-h1 (More than one ); noindex (The page carries a robots noindex directive); redirect-chain (The URL went through 2 or more redirects); missing-canonical (No on an indexable page).
Inputs: type, limit.
get_pageGet one pageA
Return everything the crawl recorded about one URL (status, title, meta description, H1 count, canonical, robots, redirects, broken links out).
Inputs: url (required).
list_broken_linksList broken internal linksA
Broken internal links as source page → broken target pairs, so you know which page to fix. Needs a live crawl or crawlcove-cli dataset; a desktop export lists the broken pages instead (its link graph lives in the app).
Inputs: limit.
list_pagesList pagesA
List crawled pages with status and title, optionally filtered by status code, indexability, or a URL substring.
Inputs: limit, status, indexable, urlContains.
load_exportLoad a crawl exportA
Load a Crawl Cove desktop app JSON export (Reports → Export → JSON) or a crawlcove-cli JSON result from disk and make it the active dataset. Desktop exports carry more per-page data (depth, word count, content type) and have no page cap.
Inputs: path (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
crawl_site and load_export both establish the active dataset but are clearly differentiated by source (live crawl vs. file import). The four query tools target distinct resources (issues, page details, broken link pairs, page list) with no meaningful overlap.
All tools use snake_case verb_noun, with a small set of verbs (crawl, load, get, list) that accurately reflect actions. No inconsistent naming conventions.
Six tools is well-scoped for a crawl-audit MCP: two ingestion paths, two listing/query tools, and two issue-focused tools. No obvious bloating or missing essential utility tools.
Core lifecycle is covered: ingest (live or export), list pages, inspect a page, list issues, and trace broken links. A site-level summary/statistics tool or a way to clear/switch datasets would round it out, but agents can work around these gaps.
Maintenance
Related MCP Connectors
Audit any site's AI visibility from your assistant: crawler access, rendering, and schema.
Run full technical SEO audits of any website from your AI agent and get structured findings back.
Live SEO intelligence, rank tracking, site audits, and backlink analysis for AI agents.
Your agent needs to crawl a site and say what is wrong with it — broken tags, duplicate content, pages nothing can index, resources that never load. **What you can ask for** • "Crawl this site and list every page with a duplicate title or missing description." • "Which pages are non-indexable, and why?" • "Run Lighthouse on these URLs and give me the failing audits." • "Show the internal link graph and the orphan pages." • "Give me this page's raw HTML and its microdata." **How to use it** Point any MCP client at https://mcp.aisa.one/seo-onpage/mcp and sign in with OAuth — there is no key to create or paste. 20 tools: submit a crawl and read its summary, pages, resources, links and waterfall; duplicate content and duplicate tags; keyword density; non-indexable and uncrawlable resources; parsed content, raw HTML, microdata, screenshots and Lighthouse. **Why this rather than the source** A crawler you drive from the agent, with the audit results as structured data rather than a PDF. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Find the broken pages here, then ask the same agent what those pages used to rank for — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/seo/mcp for all of it at once — rankings, keywords, backlinks, site health and AI-answer visibility across DataForSEO, Semrush and Ahrefs.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables SEO auditing and site analysis by crawling websites, identifying issues, and generating reports like sitemaps and markdown exports.513 npm4MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to analyze Screaming Frog SEO Spider crawl data through tool calls, supporting audits for broken links, redirects, indexability, and more.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to crawl and audit websites for SEO issues, returning structured JSON reports with errors, warnings, and key statistics.MIT
- FlicenseNot gradedqualityBmaintenanceEnables an AI agent to run and query self-hosted SEO crawls directly, returning findings grouped by check with evidence, stable issue ids, and a one-line fix ready to become tickets. Ships ten read-only-by-default, unmetered tools so a request to crawl a site and report what to fix comes back as actionable issues rather than a CSV.11-