In-depth architectural comparison of the Spaceship MCP and Cloudflare MCP Pro 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
Spaceship MCP
Cloud Platforms · Local stdio
Quality: 55/100 (Good) | Auth: API Key required
Cloudflare MCP Pro
Cloud Platforms · Local stdio
Quality: 60/100 (Good) | Auth: API Key required
Verdict Summary: Choose Spaceship MCP if you need specialized Cloud Platforms tools running via a local process. Choose Cloudflare MCP Pro if your workspace requires Cloud Platforms integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Spaceship MCP when:
You need dedicated capabilities in the Cloud Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: SPACESHIP_API_KEY, SPACESHIP_API_SECRET.
Manage domains, DNS records, contacts, marketplace listings, and more via the Spaceship API
The most complete Cloudflare MCP — 69 tools over the REST API v4 (DNS, Zones, Workers, KV, R2, D1, Pages, WAF, SSL, Email Routing, Logpush, Workers AI) in a single local stdio server, with a server-side human-approval gate on every mutation. npx -y cloudflare-mcp-pro.
Spaceship MCP is categorized under Cloud Platforms and uses a local stdio subprocess. In contrast, Cloudflare MCP Pro belongs to Cloud Platforms using local stdio subprocess. Select Spaceship MCP when you need capabilities focused on cloud platforms and Cloudflare MCP Pro when you require tools for cloud platforms.