Seo Monster

What seo-monster does

seo-monster brings search and site data into an MCP-compatible AI client without requiring a separate dashboard. Its main data sources are Google Search Console, GA4, PageSpeed Insights, CrUX, and Cloudflare. The server can identify properties and zones, query performance metrics, inspect URLs, review sitemaps, analyze landing pages, and compare SEO results across time periods.

Search Console capabilities cover query and page rankings, clicks, impressions, CTR, position, index status, sitemap state, query opportunities, content gaps, emerging queries, cannibalization signals, and changes in page visibility. GA4 tools report landing-page performance, channel traffic, organic-search trends, conversions, internal site-search activity, and measurement readiness.

PageSpeed tools return Lighthouse scores, lab Core Web Vitals, available field data, performance opportunities, and SEO audit findings. Cloudflare tools list accessible zones and provide zone-level details such as status, plan, pause state, nameservers, and timestamps.

How it works

The MCP host launches seo-monster as a local stdio process. The server sends selected requests to the relevant provider using the credentials configured by the user, then returns a consistent JSON result structure for the assistant to interpret. It does not require a hosted account or send credentials to a separate service.

Call system_status first when the environment is unclear. It reports configured services, reachability, Google authentication details and scopes, destructive-mode status, and the available tool catalog. Setting probe=true performs a low-cost live check for each configured service; the default only inspects configuration.

Setup and configuration

The package is published as seo-monster and can be launched with uvx seo-monster. The uvx route requires Python 3.11 or newer and uv. A basic MCP configuration is:

{
  "mcpServers": {
    "seomonster": { "command": "uvx", "args": ["seo-monster"] }
  }
}

Google authentication can be initiated with uvx --from seo-monster seo-monster auth. Credentials are resolved at runtime from the user’s environment or configuration file. The Claude Desktop bundle supports macOS and Windows and supplies its Python runtime; Cursor, Cline, Codex, and advanced Claude Desktop setups can use the uvx path. GUI clients may need the absolute path to uvx.

SEO_MCP_ALLOW_DESTRUCTIVE enables gated Cloudflare write operations. Routine sitemap submission and indexing requests are available by default but still require the relevant Google scopes.

Tools and capabilities

• Discover Search Console properties and permissions with gsc_list_properties.
• Query Search Console metrics with dimensions, date ranges, filters, and data-state selection.
• Compare periods, find rising or declining pages, identify query gaps, and inspect query-to-page relationships.
• Inspect one URL or batches of up to 25 URLs, including index verdicts, crawl details, canonicals, and mobile or rich-result summaries.
• List or submit sitemaps and request indexing for one URL or batches of up to 100 URLs.
• Run flexible GA4 reports and review organic landing pages, channels, conversions, site search, and configuration readiness.
• Analyze PageSpeed lab results, field Core Web Vitals when available, estimated savings, and SEO audits.
• List Cloudflare zones and retrieve hostname-level zone information.

Limitations and notes

Search Console coverage auditing is heuristic: it bulk-inspects a user-supplied URL list because the public API does not expose the full Coverage report. Batch inspection collects per-URL failures instead of treating one transient error as a total failure. GA4 dates accept ISO dates and relative values such as 28daysAgo and today.

PageSpeed opportunities use lab data; real-user metrics should be obtained through the available CrUX-oriented analysis. Indexing and sitemap operations depend on Google API access and the scopes granted to the authenticated account. Cloudflare destructive operations have additional safeguards, including the destructive-mode setting and, for higher-risk actions, a per-call confirmation token.