seo MCP server
Commit Nov 2, 2026Performs SEO audits, website crawling, and real-time web monitoring via Firehose to identify technical, content, and performance issues.
Also known as Stackwise-digital/seo-mcp
- Stars
- 3
- Tools
- 18
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 2, 2026
- License
- MIT
What is seo MCP?
seo performs SEO audits, website crawling, and real-time web monitoring via Firehose to identify technical, content, and performance issues. It exposes 18 tools, such as scan_url, scan_site, get_site_overview.
Summary generated from the project's README
About seo MCP server
Auditing websites for technical and content issues directly from your AI chat interface is what seo-mcp enables. This open-source server runs locally and connects to clients like Claude Desktop, Claude Code, and Cursor. It allows developers and SEO specialists to perform deep scans of single URLs or entire domains using multi-threaded scanning to check 28 specific rules covering meta tags, content hierarchy, technical configurations, and performance metrics.
Users can perform site crawls with configurable depth and page limits while respecting robots.txt files. For those needing to track changes over time, the server integrates with Firehose to provide real-time web monitoring. This optional feature requires a Firehose management key and allows for monitoring content changes via Lucene queries and SSE streaming. The core scanning tools function without any API keys, as the connected LLM performs the analysis on the structured data returned by the server.
What you can do with it
- 1Perform a single page auditAsk the AI to scan a specific URL to identify SEO issues and metadata errors.
- 2Crawl an entire websiteInstruct the client to crawl a whole domain with a specific page limit to find duplicate content or broken links.
- 3Monitor competitor content changesSet up a real-time monitor to track when a competitor adds new content to their site.
- 4Analyze content quality deeplyRequest a detailed breakdown of a page's keywords and technical structure.
Written from the project's README. Every use case is checked against a quote from it.
seo MCP tools 18
Detected from the READMEscan_urlscan_siteget_site_overviewanalyze_pagefirehose_monitorfirehose_manage_tapsfirehose_manage_rulesfirehose_streamaddedremovedtitleurl
| scan_url | — | |
| scan_site | — | |
| get_site_overview | — | |
| analyze_page | — | |
| firehose_monitor | — | |
| firehose_manage_taps | — | |
| firehose_manage_rules | — | |
| firehose_stream | — | |
| added | — | |
| removed | — | |
| title | — | |
| url | — |
Show all 18 toolsShow fewer tools
domainpage_categorypage_typelanguagepublish_timerecent
| domain | — | |
| page_category | — | |
| page_type | — | |
| language | — | |
| publish_time | — | |
| recent | — |
Configuration
FIREHOSE_MANAGEMENT_KEY
| Name | Description | |
|---|---|---|
| FIREHOSE_MANAGEMENT_KEY | — |
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablestackwise-digital/seo-mcp is public and reachablegithub.com/stackwise-digital/seo-mcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-02github.com/stackwise-digital/seo-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model18 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubseo-mcp
Free, open-source MCP server for scanning websites for SEO issues — runs locally and integrates directly with Claude Desktop, Claude Code, Cursor, and other MCP clients.
No API keys required for core functionality. The conversation LLM performs AI analysis directly.
Website: seo-mcp.dev · Built by larch, a product studio that ships MVPs, mobile apps and AI tools.
Features
- 28 SEO rules across meta, content, technical, and performance categories
- Multi-threaded scanning with
worker_threadsfor parallel page analysis - Site crawling with configurable depth, page limits, and robots.txt respect
- Deep page analysis — returns structured data for the conversation LLM to analyze (no API key needed)
- Real-time web monitoring via Firehose (Ahrefs) — track content changes with Lucene queries and SSE streaming
- Structured results with severity levels and actionable recommendations
Getting Started
Prerequisites
- Node.js >= 20.0.0
- An MCP client: Claude Desktop, Claude Code, Cursor, or any MCP-compatible client
Installation
git clone https://github.com/Stackwise-digital/seo-mcp.git
cd seo-mcp
npm install
npm run build
Setup
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"seo-mcp": {
"command": "node",
"args": ["/path/to/seo-mcp/dist/index.js"]
}
}
}
Claude Code
Add to your Claude Code MCP settings (~/.claude/.mcp.json):
{
"mcpServers": {
"seo-mcp": {
"command": "node",
"args": ["/path/to/seo-mcp/dist/index.js"]
}
}
}
Cursor
Add to your Cursor MCP settings:
{
"mcpServers": {
"seo-mcp": {
"command": "node",
"args": ["/path/to/seo-mcp/dist/index.js"]
}
}
}
That's it — the 4 core SEO tools are ready to use. No API keys needed.
Enable Real-Time Monitoring (optional)
To use the Firehose real-time web monitoring tools:
- Sign up at firehose.com (free during beta, no credit card)
- Create a management key (starts with
fhm_) - Add it to your MCP config:
{
"mcpServers": {
"seo-mcp": {
"command": "node",
"args": ["/path/to/seo-mcp/dist/index.js"],
"env": {
"FIREHOSE_MANAGEMENT_KEY": "fhm_your_key_here"
}
}
}
}
Tools
SEO Scanning
| Tool | Description |
|---|---|
scan_url |
Scan a single URL for SEO issues. Returns score, issues by severity, metadata, links, and images. |
scan_site |
Crawl and scan an entire website. Includes duplicate content detection, robots.txt and sitemap analysis. |
get_site_overview |
Summary of a previously scanned domain — overall score, top issues, worst pages. |
analyze_page |
Deep analysis returning structured data + HTML for the LLM to provide keyword, content quality, and technical insights. |
Real-Time Monitoring (Firehose)
Powered by Ahrefs' crawler (8B+ pages/day). Requires FIREHOSE_MANAGEMENT_KEY.
| Tool | Description |
|---|---|
firehose_monitor |
Quick setup — create a tap and monitoring rule in one step. Ideal after an SEO audit. |
firehose_manage_taps |
Create, list, or delete monitoring taps. |
firehose_manage_rules |
CRUD rules using Lucene query syntax (e.g., domain:example.com AND added:"pricing"). |
firehose_stream |
Consume real-time change events. Supports replay via 24h buffer. |
| Field | Type | Description |
|---|---|---|
added |
text | Newly inserted content (default search field) |
removed |
text | Deleted content |
title |
text | Page title |
url |
keyword | Full URL (exact match) |
domain |
keyword | Domain (e.g., example.com) |
page_category |
keyword | ML category (e.g., /News, /Finance) |
page_type |
keyword | ML type (e.g., /Article/How_to) |
language |
keyword | ISO 639-1 code (e.g., en) |
publish_time |
keyword | ISO-8601 datetime |
recent |
filter | Recency filter (e.g., 24h, 7d) |
Supports: AND, OR, NOT, phrases ("..."), wildcards (*, ?), ranges ([... TO ...]). Max 25 rules per org.
Example Workflows
Audit a single page:
"Scan https://example.com for SEO issues"
Crawl an entire site:
"Scan site example.com with max 100 pages"
Deep analysis:
"Analyze https://example.com focusing on keywords and content quality"
Monitor a competitor after audit:
"Set up a Firehose monitor for competitor.com" "Stream the latest events from that monitor"
Track specific content changes:
"Create a Firehose monitor with query: domain:example.com AND added:"pricing" AND language:"en""
SEO Rules (28 total)
| Category | Rules |
|---|---|
| Meta (10) | Title exists, title length, description exists, description length, canonical URL, Open Graph tags, Twitter card, viewport, hreflang, favicon |
| Content (7) | H1 exists, H1 count, heading hierarchy, image alt text, word count, internal links, broken links |
| Technical (7) | HTTPS, status code, robots meta/noindex, structured data, redirect chains, lang attribute, DOCTYPE |
| Performance (4) | Page size, response time, compression, cache headers |
Configuration
All configuration is via environment variables. Defaults work out of the box.
| Variable | Default | Description |
|---|---|---|
WORKER_POOL_SIZE |
4 |
Number of worker threads |
DEFAULT_MAX_PAGES |
50 |
Default max pages for site crawl |
DEFAULT_MAX_DEPTH |
3 |
Default max crawl depth |
REQUEST_TIMEOUT_MS |
15000 |
HTTP request timeout |
REQUESTS_PER_SECOND |
5 |
Rate limit for outbound requests |
FIREHOSE_MANAGEMENT_KEY |
— | Firehose management key (optional, for firehose_* tools) |
See .env.example for a template.
Development
npm install # Install dependencies
npm run dev # Run in dev mode (no build needed)
npm run build # Build
npm run typecheck # Type check
npm test # Run tests
Architecture
src/
├── index.ts # MCP server entry point
├── config/ # Environment-based configuration
├── types/ # TypeScript type definitions
├── tools/ # MCP tool registrations (8 tools)
├── scanner/ # Core scanner engine, fetcher, parser, crawler
├── rules/ # 28 SEO rules across 4 categories
├── workers/ # worker_threads pool for parallel scanning
├── firehose/ # Firehose real-time monitoring client
├── store/ # In-memory result storage
└── utils/ # Rate limiter, URL utils, logger
Companion Tools
Bridddge — Desktop LinkedIn automation built by the same team. If you use seo-mcp to audit your content and want to amplify it on LinkedIn, Bridddge handles outreach, connection requests, and follow-ups with AI-driven personalization. Privacy-first, runs locally.
License
MIT · Built by larch
seo MCP questions
What tools does seo MCP provide?
It exposes 18 tools, including scan_url, scan_site, get_site_overview, analyze_page, firehose_monitor.
Do I need an API key to use the SEO scanning features?
No, no API keys are required for the core SEO scanning and crawling functionality.
What kind of SEO rules does the server check?
The server checks 28 rules across meta, content, technical, and performance categories.
Which MCP clients are supported?
It works with Claude Desktop, Claude Code, Cursor, and any other MCP-compatible client.