Seo Monster
Wire your coding agent to live Search Console, GA4, PageSpeed, and technical-SEO APIs so you can audit and fix SEO without leaving the editor.
Overview
seo-monster is a Launch-phase MCP server that connects your agent to Search Console, GA4, PageSpeed Insights, Cloudflare, IndexNow, CrUX, and technical-SEO workflows in one stdio package.
What is this MCP server?
- Search Console and GA4 via one-time Google OAuth (client-secrets + cached token path)
- PageSpeed Insights and CrUX for performance and field CWV signals tied to SEO
- Cloudflare and IndexNow hooks for crawl/index and CDN-side technical checks
- Default GSC property and GA4 property IDs via env for repeatable agent workflows
- stdio MCP package on PyPI (seo-monster v0.5.1) for Claude Code, Cursor, and other MCP hosts
- Package version 0.5.1 on PyPI identifier seo-monster
- MCP transport type stdio per server schema
- Seven named integration surfaces in catalog description: Search Console, GA4, PageSpeed Insights, Cloudflare, IndexNow,
Community signal: 1 GitHub stars.
What problem does it solve?
SEO data lives in half a dozen Google and web-performance dashboards, so solo builders waste time context-switching instead of fixing pages with their agent.
Who is it for?
Indie builders with a live domain who already use Claude Code or Cursor and want agent-driven SEO audits grounded in GSC, GA4, and CWV data.
Skip if: Teams with no Google property access, no public URLs yet, or anyone who only needs a one-off keyword list without API-backed measurement.
What do I get? / Deliverables
After you register the MCP server and complete OAuth once, your agent can query live SEO and analytics signals and turn them into concrete site changes in the same workflow.
- Agent-queryable Search Console and GA4 reports for your default properties
- PageSpeed Insights and CrUX-driven performance findings per URL
- Technical-SEO and indexing actions via IndexNow, Cloudflare, and related MCP tools
Recommended MCP Servers
Journey fit
Canonical shelf is Launch because the server’s purpose is search visibility—indexing, rankings, technical SEO, and Core Web Vitals—not building product features. Subphase seo matches GSC, IndexNow, CrUX, PageSpeed, and technical-SEO tooling—the core launch job of getting pages discovered and ranked.
How it compares
MCP integration to Google and performance APIs—not a markdown SEO skill or a hosted rank tracker UI.
Common Questions / FAQ
Who is seo-monster for?
Solo and indie builders who ship with MCP-capable agents and need Search Console, GA4, and technical-SEO data inside the editor.
When should I use seo-monster?
Use it during Launch and Grow when pages are public and you are debugging indexing, rankings, speed, or analytics—not before you have a site to measure.
How do I add seo-monster to my agent?
Install the PyPI package seo-monster, set SEO_MCP_GOOGLE_OAUTH_CLIENT (and optional GSC/GA4 defaults), add the stdio MCP entry in your host config, and complete the one-time browser OAuth for the token file.