Side-by-Side Model Context Protocol Comparison
Seo Performance MCP vs SEOPro AI
In-depth architectural comparison of the Seo Performance MCP and SEOPro AI 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: 61/100 (Good) | Auth: No auth required
SEOPro AI
Marketing · Remote HTTP/SSE
Quality: 43/100 (Fair) | Auth: OAuth 2.0
Verdict Summary: Choose Seo Performance MCP if you need specialized Marketing tools running via a local process. Choose SEOPro AI if your workspace requires Marketing integration with remote web transport. 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.
S
Choose SEOPro AI when:
- You need dedicated capabilities in the Marketing domain.
- You prefer remote streaming HTTP/SSE transport architecture.
- Your security boundary fits: OAuth 2.0 (Free / Open Source).
- Primary tools included: 18 narrowly scoped SEO tools, Search Console summaries, keywords, and trends, AI-referral traffic, citation, audit, and backlink analysis.
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
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
SEOPro AI Configuration