Librecrawl — Technical SEO Audit MCP Server

Librecrawl — Technical SEO Audit MCP server exists for a simple reason — assistants are far more useful when they can act on Librecrawl — Technical SEO Audit directly instead of describing what you should do. Self-hosted technical SEO audit MCP. 50+ checks, WAF detection, ephemeral. Built on LibreCrawl.

What you get

Run a complete on-site SEO audit on any website — straight from Claude, Cursor, Codex, or any Model Context Protocol (MCP) client. Unlimited pages · 50+ checks · PDF + CSVs · MIT-licensed · self-hosted · ephemeral by design.

What the assistant can call

Once Librecrawl — Technical SEO Audit is connected, these are the calls the assistant has available:

• librecrawl_external_links_audit — re-run external-link validation on a specific crawl
• librecrawl_site_check — instant site-level check
• librecrawl_wipe_everything — nuclear reset to zero
• librecrawl_brain_purge_audit — purge a single audit

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration and credentials

You will need 2 environment variables: LIBRECRAWL_URL, PAGESPEED_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

This sits in the search and retrieval group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Librecrawl — Technical SEO Audit's toolset — librecrawl_external_links_audit, librecrawl_site_check, librecrawl_wipe_everything and 1 more — is a fair guide to whether it matches your workflow. It is maintained by adityaarsharma; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Librecrawl — Technical SEO Audit's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the librecrawl — technical seo audit mcp server does with a few real requests.