📑 Table of contents

• What is an MCP?
• The whole pitch in 4 lines
• One command = a complete audit
• Why this exists
• Install in 60 seconds — one-liner · Docker · manual
• 50+ checks every audit
• Feature comparison
• What every audit produces
• Your first audit
• How it works · Architecture
• Configuration
• 38 MCP tools
• Documentation
• Roadmap
• License & credits

🤔 Don't know what an MCP is? Read this 30-second explainer

Model Context Protocol (MCP) is the open standard that lets AI assistants like Claude, Cursor, or Codex call external tools. Think of it as "USB for AI assistants" — you plug a tool in, the AI can use it. librecrawl-technical-seo-audit-mcp is one of those tools. Once installed, you just ask your AI assistant to audit a site, and it does. No GUI. No dashboard. No exports.

New to all this?

• Don't have Claude Code yet? → Install Claude Code (free for individuals).
• Prefer Cursor? → Get Cursor.
• Already have one of those? → Skip to Install in 60s.

🪄 The whole pitch in 4 lines

You:    Audit https://acme.com — full site, no caps, give me the zip
Agent:  → librecrawl_start_chunked_audit · polls until done · saves zip locally
You:    Show me broken pages + broken external links + hreflang errors
Agent:  → reads CSVs, prints filtered tables. Server already forgot the audit.

That's the product. Your AI assistant runs a full technical SEO audit for you. You get a branded PDF + 7 CSVs covering 50+ technical checks, ready to hand a client. The server wipes everything the moment you download.

✅ One command = a complete audit (v2.2.0)

No flags to remember, no caps to set. Anyone who runs:

librecrawl_start_chunked_audit(url="https://yoursite.com")

gets a full end-to-end audit by default:

• Every page — entire sitemap crawled, including orphan pages not linked from the homepage
• Every page's text — readability, AI-tells, boilerplate analyzed word-by-word
• Every outbound link — every domain (yours, third-party, social, CDN) HTTP-validated for broken links
• No silent dropping — per-page checks + link validation cover 100% of pages; the report states exactly what was covered
• Heavy sites safe — 4–5 MB pages crawl fine; Screaming-Frog-grade politeness never overloads the origin
• Zero history — the server forgets the entire audit the moment you download the zip; re-scan anytime, nothing persists

Verified on real production sites: 1,942-page and 709-page WordPress sites, full coverage, origins healthy throughout.

Note: runs one audit at a time (single-tenant backend). For team use, queue audits sequentially — concurrent multi-audit routing is on the roadmap.

🔥 Why this exists

There are great desktop SEO crawlers (you know the ones). There are great cloud SEO suites. There was no AI-native crawler. librecrawl-technical-seo-audit-mcp fills that gap with five things no comparable open-source MCP server does:

⚡ It runs inside your AI assistant

38 MCP tools your agent calls directly. No GUI app to babysit, no SaaS dashboard to log into, no CSV exports to upload to ChatGPT. You just ask.

🚀 Chunked-progressive crawler that never times out

Most SEO MCP servers (SiteAudit MCP, AgentAEO, SE Ranking MCP) run synchronously and disconnect on sites over a few hundred pages. librecrawl-technical-seo-audit-mcp runs the crawl in a background worker thread, persists progress to SQLite WAL, and returns a session_id in under 2 seconds. Your agent polls a tiny status tool until done. 10,000-page enterprise sites work the same as 50-page blogs. Survives PM2 / MCP-client restarts mid-crawl.

🛡️ Catches WAF challenges other crawlers silently misreport

Cloudflare, Akamai, DataDome, Imperva, and PerimeterX challenge pages are served as 200 OK but contain a JavaScript challenge instead of your content. Most crawlers report these as "page OK, all good". librecrawl-technical-seo-audit-mcp fingerprints the challenge in the response body and flags bot_block_challenge_detected. You see what's actually broken.

🤖 An AIMD controller tunes crawl delay live

Additive-Increase / Multiplicative-Decrease — the same algorithm TCP congestion control uses. Error rate > 10% → halve chunk, double delay. p95 latency > 1.5× target → 1.5× delay. Clean signals → additive decrease. Polite by construction. No rate-limit blow-ups. No manual tuning. Respects robots.txt Crawl-Delay floor.

🧹 Ephemeral by design — the agency-safe default

Once you download the zip, the server deletes the session row, every artifact file on disk, AND the upstream LibreCrawl crawl record. Per-audit server footprint after cleanup: 0 bytes, 0 rows. Auditing 50 client sites? Zero data persists where another operator could see it.

📄 Branded PDF reports ready to hand a client

WeasyPrint, A4, page numbers, footer on every page. Open in any PDF viewer. No SaaS watermark. Hand it to a client as your work.

⚡ Install in 60 seconds

curl -fsSL https://raw.githubusercontent.com/adityaarsharma/librecrawl-technical-seo-audit-mcp/main/install.sh | bash

The installer asks 3 questions (target client, optional Google PageSpeed API key, optional GSC integration) and writes a ready-to-use MCP entry into your Claude / Cursor / Codex / Windsurf config. Done.

Three ways to run: the one-liner above (guided installer) · Docker (full stack, one command — best for self-hosting/VPS) · manual (Python venv + your own backend). New here? Start with the one-liner.

🐳 Run the full stack with Docker (recommended for self-hosting)

Brings up both the LibreCrawl engine and the MCP server, wired together and health-gated, with one command. Requires Docker + Docker Compose.

git clone https://github.com/adityaarsharma/librecrawl-technical-seo-audit-mcp.git
cd librecrawl-technical-seo-audit-mcp
docker compose up --build          # MCP at http://127.0.0.1:5081/mcp