Side-by-Side Model Context Protocol Comparison
Seo Performance MCP vs Seo Stack MCP
In-depth architectural comparison of the Seo Performance MCP and Seo Stack MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Seo Performance MCP
Marketing · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Seo Stack MCP
Marketing · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose Seo Performance MCP if you need specialized Marketing tools running via a local process. Choose Seo Stack MCP if your workspace requires Marketing integration with local subprocess execution. Both servers can be configured concurrently in your client's
mcpServers manifest.Which MCP Server Should You Choose?
Choose Seo Performance MCP when:
- You need dedicated capabilities in the Marketing domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
- Primary tools included: posts_list, posts_snapshot, posts_decay_curve.
Choose Seo Stack MCP when:
- You need dedicated capabilities in the Marketing domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
- You have access to required keys:
GOOGLE_APPLICATION_CREDENTIALS, SEO_STACK_OAUTH_CLIENT, GA4_PROPERTY_ID, GSC_SITE_URL, BING_WEBMASTER_API_KEY, BING_SITE_URL, CLARITY_API_TOKEN, ADSENSE_ACCOUNT_ID. - Primary tools included: .
Feature & Specification Comparison
Tools & Capabilities Breakdown
Seo Performance MCP Tools (9)
posts_list
Discover posts via an XML sitemap (POSTS_SITEMAP_URL or the sitemap_url arg), a JSON override list (POSTS_LIST), or - if configured - the Ghost Admin API. Pass an explicit urls[] to skip discovery entirely.
Returns metadata: url, title, published_at, age_days, tags. Filter by minimum age or published-after date.
When to use: discover which URLs are eligible for snapshot / verdict / cohort analysis. Works with any CMS that exposes a sitemap.
posts_snapshot
Pull a 30/60/90-day snapshot across every configured signal source for one post: GSC clicks/impressions/CTR/position + top queries, Matomo visits + dwell, GA4 pageviews, Clarity scroll/rage clicks, AI-citation counts.
Each source is best-effort: if its env vars are missing the field is omitted. Returns whatever is available.
Read-only. No third-party writes. Optionally persists to the local DuckDB cache when persist=true.
posts_decay_curve
Bucket GSC clicks/impressions/avg-position into ~weekly windows for the last N weeks (default 12) and classify the trend: decay / plateau / growth.
Underpins the verdict engine's decay rules. Read-only GSC query.
posts_verdict
Run the rule-based verdict engine on a single post: combine snapshot + decay curve and emit a verdict with reason codes and a 0-1 confidence score.
Reason codes are deterministic. The mapping reasons -> verdict lives in src/verdict/rules.ts and can be inspected.
Reporting only - does NOT mutate anything. To act on the verdict, hand the brief to a writer or to an AI rewrite tool.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Seo Performance MCP Configuration
Seo Stack MCP Configuration