Side-by-Side Model Context Protocol Comparison
Seo MCP vs SEOmatic
In-depth architectural comparison of the Seo MCP and SEOmatic 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 MCP
Marketing · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
SEOmatic
Marketing · Remote HTTP/SSE
Quality: 37/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Seo MCP if you need specialized Marketing tools running via a local process. Choose SEOmatic 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 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:
MCP_API_KEY, PORT, APP_API_BASE_URL, APP_PUBLIC_BASE_URL, MCP_INTERNAL_TOKEN. - Primary tools included: run_audit_anonymous, run_audit, get_audit.
Choose SEOmatic when:
- You need dedicated capabilities in the Marketing domain.
- You prefer remote streaming HTTP/SSE transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
- Primary tools included: Hosted Streamable HTTP MCP endpoint, OAuth 2.1 and Bearer API key authentication, Google Search Console performance and indexing insights.
Feature & Specification Comparison
Tools & Capabilities Breakdown
Seo MCP Tools (6)
run_audit_anonymous
Run a one-shot SEO + AI-readability audit on any public URL. Returns scores across 11 modules and ~90 checks, plus actionable findings with rule docs. Limited to 1 audit per IP per 24 hours — for higher volume, get an API key at https://app.metricspot.com/settings/api-keys and use `run_audit`. Synchronous: blocks until the audit completes. Does NOT include Core Web Vitals (use `run_audit` for full PSI scoring). No auth required.
run_audit
Queue a full SEO + AI-readability audit (includes Core Web Vitals from Google PSI and organic traffic if Google is linked). Returns the audit envelope immediately with `status: queued` and an `audit_id`. Poll `get_audit` with the returned `audit_id` until `status` becomes `complete` (typical 10-30s). Counts against the user's plan allowance. Requires an API key as a Bearer token. Quota and per-domain cooldowns mirror the dashboard.
get_audit
Fetch a previously-run audit by id. Returns module scores (0-100), total score, all findings with severity, recommendation text, and links to the HTML report. Use this to poll a queued `run_audit` until `status: complete`. Requires an API key.
list_audits
List the user's audits (most recent first, deduplicated by URL). Returns `audit_id`, `url`, `status`, `total_score`, `created_at`. Default limit 24, max 100. Use the returned `audit_id` with `get_audit` for full findings. Requires an API key.
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 MCP Configuration
SEOmatic Configuration