Purpose
eds-mcp-server is the first MCP server built specifically for Adobe Edge Delivery Services (EDS), containing a total of 41 tools. It enables AI agents to run and improve your Edge Delivery site: read content, audit issues, fix errors, publish and unpublish, with support for single-page or site-wide bulk operations, and every write can be previewed and rolled back.
Main capabilities
Preview, publish, and content management
It provides tools such as eds_preview_page, eds_publish_page, eds_unpublish_page, eds_preview_and_publish, eds_purge_cache, eds_bulk_preview, eds_bulk_publish, eds_get_job_status, eds_search_pages, eds_get_metadata, eds_get_sitemap, eds_get_redirects, covering publishing, cache purging, and bulk operations.
Document Authoring (DA) source operations
Nine tools can directly access the site's Document Authoring source (admin.da.live), the real source behind an EDS site, and require EDS_DA_TOKEN. The tools include: eds_da_list_sources, eds_da_get_source, eds_da_get_versions, eds_da_put_source, eds_da_delete_source, eds_da_copy_source, eds_da_move_source, eds_da_rollback, eds_da_export / eds_da_push. Among them, eds_da_export / eds_da_push let an agent export an entire DA subtree without a local checkout or aem-cli, make changes, and then bulk push them. eds_da_push supports dryRun: true to preview the results of bulk edits (created/updated/unchanged, with line diff counts), as well as withUndo: true to make writes reversible, returning an undo object to pass to eds_da_rollback to restore the previous content and remove newly created documents.
Content auditing
eds_audit_site scans the entire site or a subtree and returns a prioritized list of issues, covering SEO (missing title/description, no H1, blocked from indexing), accessibility (images without alt text, missing landmarks, form inputs without labels), content freshness (not updated for over a year), sitemap coverage, and, when a domain is provided, performance (Core Web Vitals) and 404s evaluated using Adobe's real user data. eds_audit_page runs on a single page. eds_audit_report can generate an HTML report from the audit results, including an executive summary, dimension-by-dimension health scores, prioritized issues and remediation suggestions, and a Save-as-PDF button; branding information can be passed in for white-labeling. eds_audit_snapshot records each audit score to a history table in the site content (private by default) and shows the change from last time; eds_audit_trend generates a shareable HTML trend chart. eds_audit_monitor, in automated runs, audits, compares with the last snapshot, and reports ok / degraded / broken status, and can notify Slack/Discord via webhook.
Safe fixes
eds_fix_metadata fixes page titles, meta descriptions, and Open Graph images by editing the Document Authoring source, following the same dry-run + undo path as the write tools; the content is provided by the agent, and the tool writes idempotently. eds_bulk_fix_metadata performs bulk fixes across the entire site in one reversible operation. eds_fix_redirect fixes 404s by adding 301 rules to the site redirect table. eds_fix_audit is the agent form of "one-click fix," applying both metadata and redirect fixes in a single reversible batch.
How to use
Integration takes only three lines. The agent calls tools, and the server communicates with live EDS infrastructure. Read-only tools (content, sitemap, metadata) require no credentials. Write tools (preview, publish, cache) require an admin token. Analytics tools require EDS_DOMAIN_KEY, and DA source tools require EDS_DA_TOKEN.Requires EDS_DA_TOKEN.
Configuration and Authentication
Browser login (recommended for interactive use): Open a browser and redirect to Adobe's admin.hlx.page login (same flow as AEM CLI). The admin site token is cached in ~/.aem/auth-token.json (permissions 0600, about 24 hours) and reused automatically. Please use Chrome or Firefox — Safari blocks the local callback. EDS_API_KEY serves as the CI/automation and fallback path, and always takes priority when set. How to obtain a token: at https://admin.hlx.page/login after logging in, copy the auth_token cookie value from DevTools, or copy the x-auth-token header from an authenticated AEM Sidekick request. For persistent credentials, you can configure a site API key.
Use Cases
Suitable for teams that want to automate management of Adobe Edge Delivery Services sites through AI agents, including content publishing, bulk auditing, SEO and accessibility checks, Core Web Vitals monitoring, 404 tracking, A/B experiment viewing, redirect management, and security fixes.
Limitations
- Document Authoring tools require EDS_DA_TOKEN (Adobe IMS access token).
- Write tools require an admin token, and analytics tools require EDS_DOMAIN_KEY.
- The browser login callback is blocked in Safari.
- Document paths assume the .html extension by default (index → index.html).
- The server is based on TypeScript and @modelcontextprotocol/sdk + zod, uses stdio transport, and requires native fetch() from Node 18+.
Developer and License
Built by FocusGTS (Adobe Silver Solution Partner), licensed under Apache-2.0, with no affiliation or endorsement relationship with Adobe Inc. The architecture follows Adobe's MCP conventions (derived from adobe-rnd/da-mcp), with tool naming convention eds_{verb}_{noun}.
