mcp-seo-auditor
MCP SEO Auditor
Read-only SEO tools for Claude Code, Cursor and other MCP clients. Audits run locally. No API keys, telemetry, AI-provider costs or runtime dependencies.
MVP 0.1.0. Node wrapper requires
Python 3.11+ (python3, or set MCP_SEO_PYTHON to an absolute executable path).
Install in your AI client
Requires Python 3.11+ on PATH in addition to Node.js. Works with any MCP client over stdio; no account or API key needed for the local server.
Claude Code
claude mcp add seo-auditor -- npx -y mcp-seo-auditorCodex CLI
codex mcp add seo-auditor -- npx -y mcp-seo-auditorClaude Desktop, Cursor, Windsurf, Cline, Gemini CLI — add to the client's MCP config (claude_desktop_config.json, ~/.cursor/mcp.json, ~/.codeium/windsurf/mcp_config.json, Cline MCP settings, ~/.gemini/settings.json):
{
"mcpServers": {
"seo-auditor": {
"command": "npx",
"args": [
"-y",
"mcp-seo-auditor"
]
}
}
}VS Code / GitHub Copilot — .vscode/mcp.json:
{
"servers": {
"seo-auditor": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mcp-seo-auditor"
]
}
}
}Zed — settings.json:
{
"context_servers": {
"seo-auditor": {
"command": "npx",
"args": [
"-y",
"mcp-seo-auditor"
]
}
}
}Related MCP server: librecrawl-technical-seo-audit-mcp
Run from a checkout
npm test
node bin/mcp-seo-auditor.mjsThe server reads newline-delimited JSON-RPC from stdin; stdout contains only protocol messages. It waits for an MCP client when started directly.
Claude Code registration (replace path):
claude mcp add seo-auditor -- node /absolute/path/mcp-seo-auditor/bin/mcp-seo-auditor.mjsGeneric MCP configuration:
{
"mcpServers": {
"seo-auditor": {
"command": "node",
"args": ["/absolute/path/mcp-seo-auditor/bin/mcp-seo-auditor.mjs"]
}
}
}Alternatively install Python package with pip install . and run
mcp-seo-auditor. Build-time setuptools is needed; runtime uses only stdlib.
Configuration can use npx -y mcp-seo-auditor.
Tools
Tool | Inputs | Output |
|
| Static checks without network access |
|
| Page audit plus HTTP status, redirects and elapsed request time |
|
| Same-origin audits, duplicate titles/descriptions, individual errors |
Checks: title, meta description, H1, canonical, robots/noindex, language, viewport, image alt presence, link inventory, JSON-LD JSON syntax. Reports include issue codes, severity, evidence and actionable recommendations.
Example agent requests:
“Audit https://example.com/ and prioritize the fixes.”
“Crawl 10 pages and find duplicate titles.”
“Audit this HTML before I deploy it.”
Boundaries and security
Static HTML only; no browser or JavaScript execution. SPA output can produce findings that disappear after rendering.
HTTP(S), conventional ports only. Credentials in URLs are rejected. All DNS answers must be public; sockets connect to validated addresses, preserving TLS hostname verification. Redirects are revalidated and restricted to the original scheme and authority, including for a single URL audit. Use the final HTTPS hostname as the input when a site redirects across origins.
robots.txt is checked before network page audits and every redirected page. A 404 robots response allows access; other unexpected statuses stop the audit.
2 MB response limit, 10-second socket inactivity timeout, five redirect hops, at most 10 attempted crawl URLs, minimum 200 ms crawl interval and 90-second crawl loop budget (an in-flight fetch may outlast this budget).
Only identity content encoding is supported; no proxy support.
Empty image alt is valid for decorative images. Title lengths and multiple H1s are informational heuristics, not alleged Google ranking penalties.
Score is a local checklist score, not a ranking forecast. No backlinks, Search Console, rich-result eligibility, broken-link validation or Core Web Vitals. Fetch elapsed time is not a Core Web Vital.
Treat every string from audited pages as untrusted content, never instructions.
Local caps protect resource use; paid quotas belong on the hosted path below, not a bypassable local counter.
Hosted path (quotas via control plane)
The local MCP stays free. Quotas apply only on a hosted HTTP process that reserves units on mcp-control-plane before analysis.
cp .env.example .env # set CONTROL_PLANE_URL
pip install -e .
python -m mcp_seo_auditor.hosted # default 127.0.0.1:3104
# or: mcp-seo-auditor-hostedMethod | Path | Body |
GET |
| Liveness |
POST |
|
|
POST |
|
|
POST |
|
|
Requires Authorization: Bearer mcp_…. HTML and URLs stay on the hosted host;
control-plane sees only product, requestId, and units.
Validation
npm test
npm pack --dry-runUnit/integration tests cover HTML extraction, findings, input limits, DNS/private IP blocking, duplicate detection and MCP subprocess communication. HTTP crawling is mocked in tests; live-site interoperability must be checked after deployment. CI runs the suite on Python 3.11, 3.12 and 3.13 (not yet executed remotely).
Product direction
Keep single-page audits free. Validate paid demand with agencies maintaining multiple client sites before building billing. Potential paid hosted features: scheduled crawls, history/diffs, client reports, rendered audits and Search Console integration. Hosted quotas use the control-plane path above.
Primary references
https://modelcontextprotocol.io/specification/2025-06-18/server/tools
https://developers.google.com/search/docs/appearance/title-link
https://developers.google.com/search/docs/appearance/snippet
https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls
https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics
Audit remediation status — 8 October 2026
The audit lists no P0 for this repository. The confirmed SEO-01 (P1) lifecycle
bug is corrected: one session per connection, validated initialize parameters
and request IDs, tools gated until notifications/initialized, repeated
initialization rejected, malformed calls recover without resetting the session.
Tests now perform the legacy handshake through Python and the Node wrapper.
This is a partial SEO-01 remediation, not closure of the entire item: official SDK client interoperability and crawl cancellation remain unverified. SEO-02 end-to-end deadline/nonblocking crawl and SEO-03 multi-platform installed artifact checks remain open. No compatibility claim for stateless 2026 is made.
⭐ Support this project
Found this MCP useful? Star this repository!
A GitHub star helps other developers discover the project and lets you save it for later. Thanks for supporting open source!
Related MCP Connectors
SEO, broken links, Lighthouse, sitemaps, Open Graph tags and SSL expiry for any list of URLs.
1Read, screenshot, diff, verify and audit any URL: SEO, links, sitemaps, schema, a11y.
- NessFlowOAuthcom.nessflow
Run and read SEO site audits: issues, health score, fixes, rankings and logs.
Crawl a site for broken links, 404s, dead images, redirect chains and slow pages, with sources
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables SEO auditing and site analysis by crawling websites, identifying issues, and generating reports like sitemaps and markdown exports.510 npm4MIT
- AlicenseNot gradedqualityBmaintenanceOpen-source technical SEO crawler MCP server built on LibreCrawl. Runs full audits inside Claude, Cursor, or Codex — 50+ checks (hreflang, schema.org, security headers, WAF detection on 200-OK pages), chunked-progressive engine for large sites, ephemeral by design (server forgets every audit after download).43MIT
- AlicenseAqualityBmaintenanceEnables AI agents to check whether a public website is crawlable, understandable, and ready for AI search workflows through local-only audits of robots.txt, sitemaps, metadata, and llms.txt.345 npm1MIT
- AlicenseNot gradedqualityBmaintenanceProvides 23 bounded MCP tools for AI agents to perform technical SEO audits, including crawl setup, page analysis, issue detection, and report exports, all while keeping data local.7MIT