ConvRadar vs Seo MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
ConvRadar vs Seo MCP
In-depth architectural comparison of the ConvRadar and Seo 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
ConvRadar
Marketing · Remote HTTP/SSE
Quality: 52/100 (Good) | Auth: No auth required
Seo MCP
Marketing · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Verdict Summary: Choose ConvRadar if you need specialized Marketing tools running via a hosted cloud SSE transport. Choose Seo 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 ConvRadar 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).
ConvRadar is categorized under Marketing and uses a remote streaming HTTP/SSE transport. In contrast, Seo MCP belongs to Marketing using local stdio subprocess. Select ConvRadar when you need capabilities focused on marketing and Seo MCP when you require tools for marketing.
Score traffic sources by engagement and conversion quality.
cr_detect_traffic_quality_change
Step-changes in traffic quality over a window.
cr_get_device_breakdown
Sessions and conversions by device category.
cr_get_geo_breakdown
Sessions and conversions by country and region.
cr_get_landing_pages
Top landing pages with engagement and conversion.
+27 more tools listed on main page
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.
get_audit_pdf
Return a signed download URL for the branded PDF report for a given audit id. If no PDF has been rendered yet, queues a render and returns `status: queued` — poll the same tool again, or fetch the URL directly once ready. Requires an API key.
get_organic_traffic
If the user has linked GA4 + Google Search Console, return the 28-day organic traffic snapshot for an audit: session count, daily trend, top landing pages, top queries, and indexing health. Returns `connected: false` if Google is not linked. Cached 24h server-side. Requires an API key.