In-depth architectural comparison of the Eds MCP Server and Shipstatic 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
Eds MCP Server
Cloud Platforms · Local stdio
Quality: 53/100 (Good) | Auth: API Key required
Shipstatic MCP
Cloud Platforms · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Verdict Summary: Choose Eds MCP Server if you need specialized Cloud Platforms tools running via a local process. Choose Shipstatic MCP 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 Eds MCP Server when:
You need dedicated capabilities in the Cloud Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: EDS_OWNER, EDS_REPO.
Primary tools included: 20 tools for EDS publishing and content operations, Page preview, publishing, unpublishing, and cache purging, Page listing, search, metadata, sitemap, and redirect retrieval.
Eds MCP Server is categorized under Cloud Platforms and uses a local stdio subprocess. In contrast, Shipstatic MCP belongs to Cloud Platforms using local stdio subprocess. Select Eds MCP Server when you need capabilities focused on cloud platforms and Shipstatic MCP when you require tools for cloud platforms.
Adobe Edge Delivery Services (AEM EDS) management with 20 tools for preview, publish, bulk operations, content reading, Core Web Vitals, 404 tracking, A/B experiments, site configuration, and redirects. Install: npx @focusgts/eds-mcp-server.
Deploy and manage static sites from AI agents. A simpler alternative to Vercel and Netlify for static website hosting — upload files, get a URL, and connect custom domains.