Crawl and analyse websites for SEO errors using Crawlee with SQLite storage
If you already use Seo, the seo mcp server is the piece that lets your assistant work with it directly. Crawl and analyse websites for SEO errors using Crawlee with SQLite storage.
I wanted to build on my experience working with the MCP protocol SDK to see just how far we can extend an AI assistant's capabilities. I decided that I'd quite like to build a crawler to check my site's "technical SEO" health and came across Crawlee - which seemed like the ideal library to base the crawl component of my MCP.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Credits — The core crawling architecture is inspired by the logic and patterns from the LibreCrawl project. We'verun_seo_audit — Crawl a website and extract comprehensive SEO data into SQLiteanalyze_seo — The analyze_seo tool exposed by this serverquery_seo_data — The query_seo_data tool exposed by this serverlist_seo_queries — The list_seo_queries tool exposed by this serverConfiguration is passed through the environment: OUTPUT_DIR, DEBUG. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Installation goes through your MCP client rather than a global install: point it at @houtini/seo-crawler-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Among the search and retrieval options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Seo's toolset — Credits, run_seo_audit, analyze_seo and 2 more — is a fair guide to whether it matches your workflow. It is maintained by houtini-ai; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Credits | The core crawling architecture is inspired by the logic and patterns from the [LibreCrawl](https://github.com/libre-crawl/core) project. We've adapted their proven crawling methodology for use within the MCP protocol whi |
| run_seo_audit | Crawl a website and extract comprehensive SEO data into SQLite. |
| analyze_seo | The analyze_seo tool exposed by this server. |
| query_seo_data | The query_seo_data tool exposed by this server. |
| list_seo_queries | The list_seo_queries tool exposed by this server. |
{
"mcpServers": {
"seo-crawler-mcp": {
"command": "npx",
"args": ["-y", "@houtini/seo-crawler-mcp"],
"env": {
"OUTPUT_DIR": "C:\\seo-audits"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| OUTPUT_DIR | Filesystem location the server is allowed to use. | Optional |
| DEBUG | Configuration value read at startup. | Optional |
The simplest web tool that matters — fetch any URL and get model-ready markdown back.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Search built for AI, not humans — semantic web search that returns model-ready content, plus code context.
Answers, not links — delegate questions to Perplexity's search-grounded models and get cited responses back.
Put 6,000+ pre-built scrapers at your assistant's fingertips through one MCP endpoint.