mcpField
L
Librecrawl Technical Seo Audit Mcp

Librecrawl Technical Seo Audit Mcp

Local
github.comDeveloper Tools44Updated 2d ago

About Librecrawl Technical Seo Audit Mcp

Sitewalk is a self-hosted MCP server that runs the LibreCrawl engine for technical SEO audits. It is for teams and site owners who want ranked findings, suggested fixes, and downloadable reports through an AI assistant, with crawl activity kept on their machine except for requests to audited sites.

Key features

  1. 0130+ technical SEO checks
  2. 02Impact-ranked findings and fixes
  3. 03PDF, Markdown, and CSV reports
  4. 04Chunked crawling and adaptive delay
  5. 05WAF challenge detection

Use cases

  1. 01Audit a site for technical SEO issues
  2. 02Review schema, hreflang, and security findings
  3. 03Export audit results for sharing or review

MCP support

The MCP server exposes 38 audit tools to compatible clients over Streamable HTTP, with stdio options documented. It runs locally and returns audit findings and report files to the assistant.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"librecrawl-technical-seo-audit": {
"command": "npx",
"args": [
"-y",
"mcp-remote"
]
}
}
}
Run commandnpx -y mcp-remote

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmmcp-remote

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README
Sitewalk logo

Sitewalk: technical SEO audit MCP server

Ask your AI assistant to audit a website. Get the technical SEO problems back, ranked by impact, with a plain fix for each.

License: MIT MCP Compatible Latest Release Powered by LibreCrawl


This repository is the Sitewalk MCP server and nothing else: a Python server that drives the open-source LibreCrawl crawler, runs 30+ technical SEO checks, and hands your AI assistant a ranked report plus a zip of PDF and CSVs. It runs on your own machine, with no account, no sign-in and no page cap. Nothing leaves your machine except the requests the crawler makes to the site you audit.

Prefer not to host anything? The same audit is available as an app inside ChatGPT.

Set it up on your machine

You need Docker running. Then:

git clone https://github.com/adityaarsharma/sitewalk.git
cd sitewalk
./setup.sh

The script checks your machine, asks one optional question (a Google PageSpeed key), builds and starts the stack, waits until the MCP server answers, and prints exactly how to connect your assistant. The first build takes a few minutes.

CommandWhat it does
./setup.shGuided setup
./setup.sh --yesSame, no questions
./setup.sh --checkOnly check that your machine can run it
./setup.sh --updatePull the newest release and rebuild
./setup.sh --stopStop it (your reports are kept)

Without Docker, see the manual route in docs/GETTING-STARTED.md.

Connect an assistant

The server listens on http://127.0.0.1:5081/mcp (streamable HTTP).

  • ChatGPT and Grok reach servers over the internet, so they need a public https address that forwards to your machine. The server has no sign-in of its own, so put it behind a tunnel that adds access control. Steps in docs/GETTING-STARTED.md.
  • Clients on your computer (Codex, Windsurf, any stdio-only client) connect through mcp-remote:
{
  "mcpServers": {
    "sitewalk": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "http://127.0.0.1:5081/mcp"]
    }
  }
}

Then ask: Audit https://yoursite.com for technical SEO problems.

What you get

  • 30+ checks per audit (broken links, redirects, canonicals, titles and descriptions, headings, schema, images, hreflang, sitemap gaps, and more). Full list and the nine report files: docs/CHECKS.md.
  • A branded PDF, a Markdown copy and CSVs, zipped in ./reports.
  • Chunked crawling that does not time out, WAF challenge detection, and a crawl delay that adapts to the site.
  • 38 MCP tools: docs/TOOLS.md.

Docs

GuideWhat is inside
Getting startedDocker and manual setup, connecting clients, your first audit
ConfigurationEvery environment variable, HTTP and stdio transport
ToolsAll 38 MCP tools
ChecksThe 30+ checks and the report files
ArchitectureHow the pieces fit
TroubleshootingCommon errors and fixes

Releases

Every change to the code that lands on main is tested and published as a new GitHub release automatically. Update with ./setup.sh --update.

Licence and credits

Code is MIT: see LICENSE and NOTICE.md. Built on LibreCrawl (MIT), FastMCP and WeasyPrint. No telemetry.

Built by Aditya Sharma.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.