Data · Local MCP server
Seo Stack MCP
The complete open-source SEO data stack for AI agents: 7 sources, 86 tools, one MCP server.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Raffaele86/seo-stack-mcp- Version
- 0.2.0
- Status
- Active
- Category
- data
- Transport
- stdio (local process)
- Package
- PyPI
- Published
- 2026-07-19
- Updated
- 2026-07-19
- Publisher
- Raffaele86 (GitHub) · 2 servers with pages here
- Repository
- github.com/Raffaele86/seo-stack-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPI | seo-stack-mcp | 0.2.0 | stdio |
How to connect Seo Stack MCP
Seo Stack MCP runs locally from a Python package published to PyPI: seo-stack-mcp version 0.2.0. 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-stack-mcp. It reads these environment variables: GOOGLE_APPLICATION_CREDENTIALS, SEO_STACK_OAUTH_CLIENT, GA4_PROPERTY_ID, GSC_SITE_URL, ADSENSE_ACCOUNT_ID, ADSENSE_CURRENCY, BING_WEBMASTER_API_KEY (secret), BING_SITE_URL, CLARITY_API_TOKEN (secret), GOOGLE_ADS_DEVELOPER_TOKEN (secret), GOOGLE_ADS_CLIENT_ID, GOOGLE_ADS_CLIENT_SECRET (secret), GOOGLE_ADS_REFRESH_TOKEN (secret), GOOGLE_ADS_CUSTOMER_ID, GOOGLE_ADS_LOGIN_CUSTOMER_ID and OPENPAGERANK_API_KEY (secret); 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-stack-mcp": {
"command": "uvx",
"args": [
"seo-stack-mcp"
],
"env": {
"GOOGLE_APPLICATION_CREDENTIALS": "<value>",
"SEO_STACK_OAUTH_CLIENT": "<value>",
"GA4_PROPERTY_ID": "<value>",
"GSC_SITE_URL": "<value>",
"ADSENSE_ACCOUNT_ID": "<value>",
"ADSENSE_CURRENCY": "<value>",
"BING_WEBMASTER_API_KEY": "<secret>",
"BING_SITE_URL": "<value>",
"CLARITY_API_TOKEN": "<secret>",
"GOOGLE_ADS_DEVELOPER_TOKEN": "<secret>",
"GOOGLE_ADS_CLIENT_ID": "<value>",
"GOOGLE_ADS_CLIENT_SECRET": "<secret>",
"GOOGLE_ADS_REFRESH_TOKEN": "<secret>",
"GOOGLE_ADS_CUSTOMER_ID": "<value>",
"GOOGLE_ADS_LOGIN_CUSTOMER_ID": "<value>",
"OPENPAGERANK_API_KEY": "<secret>"
}
}
}
}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 from Raffaele86 (GitHub)
| Server | Runs |
|---|---|
| Local Leads MCPFind local businesses with no website via OpenStreetMap, then verify them. No API keys needed. | Local · stdio |
More data servers
| Server | Runs |
|---|---|
| Seo MonsterLocal-first SEO MCP: track AI citations, Search Console, GA4, PageSpeed, Cloudflare, IndexNow, CrUX. | Local · 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 Tools: A-Parser bridgeBridge to a self-hosted A-Parser: SERP, suggests and 150+ parsers via its API (read-only). | Local · stdio |
| SEO Tools: Google Analytics 4Google Analytics 4: reports, traffic sources, landing pages, events, realtime (read-only). | Local · stdio |
| SEO Tools: Google Search ConsoleGoogle Search Console: Search Analytics, URL Inspection, sitemaps (read-only, OAuth/service acct). | Local · stdio |
| SEO Tools: Yandex WordstatMCP server for Yandex Wordstat keyword frequencies (official API v2). Free Yandex Cloud Search API. | Local · stdio |