EDS MCP Server

MCP server for Adobe Edge Delivery Services. Gives AI agents (Claude Code, Cursor, GitHub Copilot) programmatic access to EDS operations — preview, publish, read content, query performance metrics, and manage site configuration.

20 tools. Zero dependencies beyond the MCP SDK. Works with any EDS site.

Quick Start

Claude Code

claude mcp add eds -e EDS_OWNER=your-org -e EDS_REPO=your-site -- npx @focusgts/eds-mcp-server

Cursor

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "eds": {
      "command": "npx",
      "args": ["@focusgts/eds-mcp-server"],
      "env": {
        "EDS_OWNER": "your-org",
        "EDS_REPO": "your-site"
      }
    }
  }
}

VS Code (GitHub Copilot)

Add to .vscode/mcp.json:

{
  "servers": {
    "eds": {
      "command": "npx",
      "args": ["@focusgts/eds-mcp-server"],
      "env": {
        "EDS_OWNER": "your-org",
        "EDS_REPO": "your-site"
      }
    }
  }
}

Configuration

Variable	Required	Description
EDS_OWNER	Yes	GitHub org/user that owns the EDS site repo
EDS_REPO	Yes	GitHub repository name
EDS_REF	No	Git branch (default: main)
EDS_API_KEY	No	Admin API key for preview/publish/cache operations
EDS_DOMAIN_KEY	No	OpTel domain key for analytics queries

Read-only tools (content, sitemap, metadata, query index) work with no keys at all. Write tools (preview, publish, cache purge) need EDS_API_KEY. Analytics tools (CWV, 404s, experiments) need EDS_DOMAIN_KEY.

Tools

Publishing Operations

Tool	Description
eds_preview_page	Trigger preview for a page so content source changes appear on *.aem.page
eds_publish_page	Publish a page from preview to the live production domain (*.aem.live)
eds_unpublish_page	Remove a page from the live site
eds_preview_and_publish	Preview and publish a page in a single atomic operation
eds_get_status	Get preview, live, and code-bus status for a resource
eds_purge_cache	Purge CDN cache for a page path

Bulk Operations

Tool	Description
eds_bulk_preview	Preview multiple pages in one call (up to 100 paths)
eds_bulk_publish	Publish multiple pages in one call (up to 100 paths)

Content Reading

Tool	Description
eds_get_page	Fetch rendered page content via .plain.html
eds_list_pages	Query the site's page index with pagination
eds_search_pages	Search pages by keyword across titles, descriptions, and paths
eds_get_metadata	Fetch the site metadata sheet
eds_get_sitemap	Fetch and parse sitemap.xml
eds_get_redirects	Fetch and parse the redirects spreadsheet

Analytics (OpTel)

Tool	Description
eds_get_cwv	Core Web Vitals (LCP, CLS, INP, TTFB) by page
eds_get_404s	404 error report with hit counts and referrers
eds_get_experiments	A/B experiment results with conversion rates

Configuration

Tool	Description
eds_get_config	Read site configuration
eds_get_logs	Project activity log (preview, publish, config actions)
eds_get_api_keys	List API keys configured for the site

Examples

Once connected, ask your AI agent:

"What pages are on this EDS site?"           -> eds_list_pages
"Find all pages about pricing"               -> eds_search_pages
"Show me the content of the about page"      -> eds_get_page
"What are the Core Web Vitals for this site?" -> eds_get_cwv
"Preview and publish the homepage"           -> eds_preview_and_publish
"Publish all blog posts"                     -> eds_bulk_publish
"Are there any 404 errors on the site?"      -> eds_get_404s
"Show me the redirect rules"                 -> eds_get_redirects
"Show me the site configuration"             -> eds_get_config

How It Works

This is a local MCP server that runs on your machine via stdio. When you connect it to Claude Code, Cursor, or another MCP-compatible AI tool, the agent can call these tools to interact with your EDS site's real APIs:

• Admin API (admin.hlx.page) for preview, publish, cache, config, and logs
• Content API (*.aem.live) for page content, query index, metadata, and sitemap
• OpTel API (rum.hlx.page) for Core Web Vitals, 404 tracking, and experiment data

No sandbox or local AEM instance needed. The server talks directly to the live EDS infrastructure.

Architecture

Built following Adobe's MCP server conventions (derived from adobe-rnd/da-mcp):

• TypeScript + @modelcontextprotocol/sdk + zod
• Stateless per-request
• Tool naming: eds_{verb}_{noun}
• Stdio transport for local use
• Native fetch() (Node 18+, zero HTTP dependencies)

Development

git clone https://github.com/focusgts/eds-mcp-server.git
cd eds-mcp-server
npm install
npm run build
npm test

Related Tools

Tool	What it does
eds-content-ops-skills	43 AI skills for EDS content ops — auditing, SEO, accessibility, blocks, migration, and more. Pair with this MCP server for automated workflows.
@focusgts/eds-ops	CLI health scanner and GitHub Action for automated site grading and PR gating.
EDS Score	Free browser-based site health analyzer for EDS sites.

About

Built by FocusGTS — Adobe Silver Solution Partner specializing in Edge Delivery Services.

License

Apache-2.0