seo-monster — Claude Code MCP server: SEO answers in chat
A local MCP server that answers SEO questions inside your assistant, pulling Search Console, GA4, PageSpeed and Cloudflare data from your own machine.
claude mcp add --env SEO_MCP_GOOGLE_OAUTH_CLIENT=<SEO_MCP_GOOGLE_OAUTH_CLIENT> --env SEO_MCP_GOOGLE_TOKEN=<SEO_MCP_GOOGLE_TOKEN> --env SEO_MCP_GSC_DEFAULT_SITE=<SEO_MCP_GSC_DEFAULT_SITE> --env SEO_MCP_GA4_PROPERTY_ID=<SEO_MCP_GA4_PROPERTY_ID> --env PSI_API_KEY=<PSI_API_KEY> --transport stdio seo-monster -- uvx seo-monsterWhat seo-monster does
seo-monster runs as a stdio MCP server and hands your assistant 70 tools: Search Console, GA4, PageSpeed, CrUX, Cloudflare, IndexNow, brand mentions in AI search answers, keyword discovery and technical checks. Every call returns the same JSON envelope, so replies stay readable in chat. Thirteen named workflow prompts ship with it.
Install runs through uvx seo-monster; the package lives on PyPI. That path needs Python 3.11 or newer plus uv, which supplies uvx. GUI hosts ignore your shell profile, so put the full path to uvx in the MCP config — which uvx prints it. Sign in to Google once with uvx --from seo-monster seo-monster auth, then have the assistant call system_status to see what is connected.
Reads always work. Two routine writes — sitemap submission and indexing requests — are enabled by default. Cloudflare write tools (cache purge, redirects, settings, robots.txt management) sit behind SEO_MCP_ALLOW_DESTRUCTIVE, and the riskiest ones also want a confirm token on the call itself. Credentials come from your environment or config file; nothing leaves your machine.
What it helps with
- find topics where the site already ranks close to the top and get a brief
- check a page for technical SEO and structured-data issues before publishing
- submit a new URL for indexing to Google, Bing and Yandex
- compare rankings before and after a change against a control group
- see how often the brand shows up in AI answer engines
Example prompts for the agent
- What should I write about next? Check Search Console and show topics at positions 8–20.
- Run the technical SEO and structured-data checks on
/blog/new-post. - Get this URL indexed and tell me what Google and Bing replied.
How to install seo-monster
Platform CLI
claude mcp add --env SEO_MCP_GOOGLE_OAUTH_CLIENT=<SEO_MCP_GOOGLE_OAUTH_CLIENT> --env SEO_MCP_GOOGLE_TOKEN=<SEO_MCP_GOOGLE_TOKEN> --env SEO_MCP_GSC_DEFAULT_SITE=<SEO_MCP_GSC_DEFAULT_SITE> --env SEO_MCP_GA4_PROPERTY_ID=<SEO_MCP_GA4_PROPERTY_ID> --env PSI_API_KEY=<PSI_API_KEY> --transport stdio seo-monster -- uvx seo-monsterReplace <…> with your own values. 14 more environment variables are in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from seo-monster <command>
Platform CLI
codex mcp add seo-monster --env SEO_MCP_GOOGLE_OAUTH_CLIENT=<SEO_MCP_GOOGLE_OAUTH_CLIENT> --env SEO_MCP_GOOGLE_TOKEN=<SEO_MCP_GOOGLE_TOKEN> --env SEO_MCP_GSC_DEFAULT_SITE=<SEO_MCP_GSC_DEFAULT_SITE> --env SEO_MCP_GA4_PROPERTY_ID=<SEO_MCP_GA4_PROPERTY_ID> --env PSI_API_KEY=<PSI_API_KEY> -- uvx seo-monsterReplace <…> with your own values. 14 more environment variables are in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from seo-monster <command>
Config file
{
"mcpServers": {
"seo-monster": {
"command": "uvx",
"args": [
"seo-monster"
],
"env": {
"SEO_MCP_GOOGLE_OAUTH_CLIENT": "<SEO_MCP_GOOGLE_OAUTH_CLIENT>",
"SEO_MCP_GOOGLE_TOKEN": "<SEO_MCP_GOOGLE_TOKEN>",
"SEO_MCP_GSC_DEFAULT_SITE": "<SEO_MCP_GSC_DEFAULT_SITE>",
"SEO_MCP_GA4_PROPERTY_ID": "<SEO_MCP_GA4_PROPERTY_ID>",
"PSI_API_KEY": "<PSI_API_KEY>"
}
}
}
}Replace <…> with your own values. 14 more environment variables are in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from seo-monster <command>
Config file
{
"servers": {
"seo-monster": {
"type": "stdio",
"command": "uvx",
"args": [
"seo-monster"
],
"env": {
"SEO_MCP_GOOGLE_OAUTH_CLIENT": "<SEO_MCP_GOOGLE_OAUTH_CLIENT>",
"SEO_MCP_GOOGLE_TOKEN": "<SEO_MCP_GOOGLE_TOKEN>",
"SEO_MCP_GSC_DEFAULT_SITE": "<SEO_MCP_GSC_DEFAULT_SITE>",
"SEO_MCP_GA4_PROPERTY_ID": "<SEO_MCP_GA4_PROPERTY_ID>",
"PSI_API_KEY": "<PSI_API_KEY>"
}
}
}
}Replace <…> with your own values. 14 more environment variables are in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from seo-monster <command>
Platform CLI
gemini mcp add -e SEO_MCP_GOOGLE_OAUTH_CLIENT=<SEO_MCP_GOOGLE_OAUTH_CLIENT> -e SEO_MCP_GOOGLE_TOKEN=<SEO_MCP_GOOGLE_TOKEN> -e SEO_MCP_GSC_DEFAULT_SITE=<SEO_MCP_GSC_DEFAULT_SITE> -e SEO_MCP_GA4_PROPERTY_ID=<SEO_MCP_GA4_PROPERTY_ID> -e PSI_API_KEY=<PSI_API_KEY> seo-monster uvx seo-monsterReplace <…> with your own values. 14 more environment variables are in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from seo-monster <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about seo-monster
How do I install seo-monster in Claude Code?
Run `claude mcp add --env SEO_MCP_GOOGLE_OAUTH_CLIENT=<SEO_MCP_GOOGLE_OAUTH_CLIENT> --env SEO_MCP_GOOGLE_TOKEN=<SEO_MCP_GOOGLE_TOKEN> --env SEO_MCP_GSC_DEFAULT_SITE=<SEO_MCP_GSC_DEFAULT_SITE> --env SEO_MCP_GA4_PROPERTY_ID=<SEO_MCP_GA4_PROPERTY_ID> --env PSI_API_KEY=<PSI_API_KEY> --transport stdio seo-monster -- uvx seo-monster. Do the one-time Google sign-in first with uvx --from seo-monster seo-monster auth`.
What does seo-monster do?
It answers SEO questions inside your assistant, pulling from Search Console, GA4, PageSpeed, CrUX, Cloudflare and IndexNow, plus keyword discovery and technical checks. 70 tools in total, all driven by your own credentials.
What do I need before it works?
Google credentials (OAuth client and token), a Search Console site identifier, a GA4 property ID and a PageSpeed Insights key. The server reads them from environment variables or a config file.
