Tempmd MCP vs Eds MCP Server — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Tempmd MCP vs Eds MCP Server
In-depth architectural comparison of the Tempmd MCP and Eds MCP Server 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
Tempmd MCP
Cloud Platforms · Local stdio
Quality: 47/100 (Fair) | Auth: No auth required
Eds MCP Server
Cloud Platforms · Local stdio
Quality: 56/100 (Good) | Auth: API Key required
Verdict Summary: Choose Tempmd MCP if you need specialized Cloud Platforms tools running via a local process. Choose Eds MCP Server 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 Tempmd MCP when:
You need dedicated capabilities in the Cloud Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: One stable, canonical URL per artifact that updates in place, Supports HTML, Markdown, CSV, and Mermaid artifacts, 7-day active window that resets on update; 7-day restore grace period after expiry.
Publish agent-made artifacts (HTML, Markdown, CSV, Mermaid) to temp.md — one stable public link that updates in place. Anonymous publish with no API key, activity-based expiry with restore. Install: npx tempmd-mcp.
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.
Category & Scope
Tools & Capabilities Breakdown
Tempmd MCP Tools (5)
One stable, canonical URL per artifact that updates in place
Supports HTML, Markdown, CSV, and Mermaid artifacts
7-day active window that resets on update; 7-day restore grace period after expiry
No account or API key required — anonymous publishing by default
Remote (10 MiB/20 files) or local stdio (50 MiB/100 files) transport
Eds MCP Server Tools (6)
20 tools for EDS publishing and content operations
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).
Tempmd MCP is categorized under Cloud Platforms and uses a local stdio subprocess. In contrast, Eds MCP Server belongs to Cloud Platforms using local stdio subprocess. Select Tempmd MCP when you need capabilities focused on cloud platforms and Eds MCP Server when you require tools for cloud platforms.