Data · Local MCP server
Seo Monster
Local-first SEO MCP: track AI citations, Search Console, GA4, PageSpeed, Cloudflare, IndexNow, CrUX.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.avansaber/seo-monster- Version
- 0.9.3
- Status
- Active
- Category
- data
- Transport
- stdio (local process)
- Package
- PyPI
- Published
- 2026-09-25
- Updated
- 2026-09-25
- Publisher
- avansaber (GitHub)
- Website
- www.avansaber.com/seomonster/
- Repository
- github.com/avansaber/seo-monster
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPI | seo-monster | 0.9.3 | stdio |
How to connect Seo Monster
Seo Monster runs locally from a Python package published to PyPI: seo-monster version 0.9.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install — the usual command is uvx seo-monster. It reads these environment variables: SEO_MCP_GOOGLE_OAUTH_CLIENT, SEO_MCP_GOOGLE_TOKEN, SEO_MCP_GSC_DEFAULT_SITE, SEO_MCP_GA4_PROPERTY_ID, PSI_API_KEY (secret), CF_API_TOKEN (secret), CF_ZONE, SEO_MCP_INDEXNOW_KEY (secret), SEO_MCP_INDEXNOW_KEY_LOCATION, SEO_MCP_ALLOW_DESTRUCTIVE, DATAFORSEO_LOGIN (secret), DATAFORSEO_PASSWORD (secret), OPENPAGERANK_API_KEY (secret), PERPLEXITY_API_KEY (secret), OPENAI_API_KEY (secret), ANTHROPIC_API_KEY (secret), GEMINI_API_KEY (secret), GOOGLE_ADS_DEVELOPER_TOKEN (secret) and GOOGLE_ADS_CUSTOMER_ID; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"seo-monster": {
"command": "uvx",
"args": [
"seo-monster"
],
"env": {
"SEO_MCP_GOOGLE_OAUTH_CLIENT": "<value>",
"SEO_MCP_GOOGLE_TOKEN": "<value>",
"SEO_MCP_GSC_DEFAULT_SITE": "<value>",
"SEO_MCP_GA4_PROPERTY_ID": "<value>",
"PSI_API_KEY": "<secret>",
"CF_API_TOKEN": "<secret>",
"CF_ZONE": "<value>",
"SEO_MCP_INDEXNOW_KEY": "<secret>",
"SEO_MCP_INDEXNOW_KEY_LOCATION": "<value>",
"SEO_MCP_ALLOW_DESTRUCTIVE": "<value>",
"DATAFORSEO_LOGIN": "<secret>",
"DATAFORSEO_PASSWORD": "<secret>",
"OPENPAGERANK_API_KEY": "<secret>",
"PERPLEXITY_API_KEY": "<secret>",
"OPENAI_API_KEY": "<secret>",
"ANTHROPIC_API_KEY": "<secret>",
"GEMINI_API_KEY": "<secret>",
"GOOGLE_ADS_DEVELOPER_TOKEN": "<secret>",
"GOOGLE_ADS_CUSTOMER_ID": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More data servers
| Server | Runs |
|---|---|
| Seo GrowthAutonomous SEO + GEO growth: keyword research, audits, content, AI answer-engine visibility. | Remote · HTTP |
| Seo KeywordsSEO Keywords MCP — search volume & difficulty via DataForSEO Labs (dataforseo.com) | Remote · HTTP |
| Seo Keywords AdsSEO Keywords (Google Ads volume) MCP — exact Google Ads search volume via. | Remote · HTTP |
| Seo MCPSix tools for SEO and AI-readability audits. 91 checks, 11 score modules. | Remote & Local · HTTP, stdio |
| SEO Page AnalyzerSEO audit any URL: meta tags, headings, links, images, Schema.org, score 0-100. x402. | Remote · SSE |
| SEO Performance MCPPer-URL SEO verdicts from GSC, GA4, Matomo, Clarity, AI citations: refresh/expand/merge/kill. | Local · stdio |
| Seo SerpSEO SERP MCP — Google organic search results via DataForSEO (dataforseo.com) | Remote · HTTP |
| Seo Stack MCPThe complete open-source SEO data stack for AI agents: 7 sources, 86 tools, one MCP server. | Local · stdio |