Eds Mcp Server
Drive Adobe Edge Delivery Services preview, publish, cache, and analytics from your agent against a GitHub-backed EDS site repo.
Overview
EDS MCP Server is an MCP server for the Build phase that provides 20 Adobe Edge Delivery Services tools for preview, publish, analytics, and content operations from your coding agent.
What is this MCP server?
- 20 tools for Adobe Edge Delivery Services content and ops
- Preview, publish, cache, and admin workflows via EDS_API_KEY
- Core Web Vitals, 404s, and experiment queries via EDS_DOMAIN_KEY (OpTel)
- stdio npm package @focusgts/eds-mcp-server v0.2.3
- Configures EDS_OWNER, EDS_REPO, and optional EDS_REF branch (default main)
- 20 tools documented for EDS preview, publish, analytics, and content ops
- Package version 0.2.3 (@focusgts/eds-mcp-server)
- stdio npm transport with five documented environment variables
What problem does it solve?
Managing EDS preview, publish, and performance data means manual Admin UI hops and scattered scripts instead of one agent-driven integration.
Who is it for?
Builders shipping marketing or docs sites on Adobe EDS who want GitHub-repo-aligned automation inside Claude Code or Cursor.
Skip if: Teams not on Edge Delivery Services or anyone who only needs a static site with no Adobe Admin or OpTel keys.
What do I get? / Deliverables
Your assistant can run EDS repo-scoped preview, publish, cache, and OpTel analytics tools from MCP without bespoke one-off scripts.
- Agent-callable EDS preview, publish, and cache operations
- OpTel-backed CWV, 404, and experiment query results in the agent thread
Recommended MCP Servers
Journey fit
EDS work centers on wiring headless content delivery and admin APIs into your build pipeline before and alongside go-live. The server is an npm stdio MCP with 20 EDS-specific tools—an integration layer to GitHub repos, Admin API, and OpTel rather than generic PM docs.
How it compares
Adobe EDS-specific MCP with 20 tools, not a generic GitHub or Vercel deploy skill.
Common Questions / FAQ
Who is EDS MCP Server for?
Developers and content engineers using Adobe Edge Delivery Services who want agent-driven preview, publish, and site analytics against their GitHub EDS repo.
When should I use EDS MCP Server?
Use it during Build integrations work and ongoing content ops when you need preview/publish, cache control, or CWV and 404 insights from OpTel.
How do I add EDS MCP Server to my agent?
Install @focusgts/eds-mcp-server via npm, run stdio MCP in your client, and set EDS_OWNER, EDS_REPO, EDS_API_KEY, and EDS_DOMAIN_KEY as documented.