Screaming Frog MCP vs Shipwork SEO Checks | AllMCPs
Side-by-Side Model Context Protocol Comparison
Screaming Frog MCP vs Shipwork SEO Checks
In-depth architectural comparison of the Screaming Frog MCP and Shipwork SEO Checks 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
Screaming Frog MCP
Marketing · Local stdio
Quality: 47/100 (Fair) | Auth: other
Shipwork SEO Checks
Marketing · Local stdio
Quality: 45/100 (Fair) | Auth: API Key required
Verdict Summary: Choose Screaming Frog MCP if you need specialized Marketing tools running via a local process. Choose Shipwork SEO Checks 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 Screaming Frog MCP when:
You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Paid Service).
Screaming Frog SEO Spider headless crawls, data export, and technical SEO audit skill for Claude. 8 tools, cross-platform (Mac + Windows), includes a ready-to-use technical SEO scan skill.
Hosted MCP tools for technical SEO audits, URL status and indexability, sitemaps, and site scores. Sign in at shipwork.io/account to create a personal MCP URL; tool calls use that account allowance.
Screaming Frog MCP is categorized under Marketing and uses a local stdio subprocess. In contrast, Shipwork SEO Checks belongs to Marketing using local stdio subprocess. Select Screaming Frog MCP when you need capabilities focused on marketing and Shipwork SEO Checks when you require tools for marketing.