claude mcp add eds-mcp-server -- npx -y eds-mcp-server
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
3 ★ · Focus-GTS/eds-mcp-server · read from the repository page · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score
score 703 · 3 ★ · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository Focus-GTS/eds-mcp-server;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
Third-party quality signals
Let an AI agent run — and *improve* — your Adobe Edge Delivery site.
**41 tools. No extra dependencies beyond the MCP SDK. Works with any EDS site.** The first MCP server purpose-built for Edge Delivery Services. **Read your content → audit it → fix what's wrong → publish → undo any of it.** One page or the whole site, in a single reversible operation. Preview before every write; undo after. --- ⚡ Do it in three lines Then just ask your agent: > *"Audit the whole site and show me what's hurting SEO."* > *"Fix the meta description on every page that's missing one — preview first, then publish."* > *"Actually, undo that whole batch."* > *"Preview and publish the homepage."* That's it — no local AEM, no scripts, no glue code. Every write is previewable and reversible. The loop that makes it different It doesn't just *drive* your site — it **improves** it, safely. Point it at an EDS site and an agent can find what's wrong and repair it, one page or the whole site in a single batch that a single eds_da_rollback reverts. No other MCP server — including Adobe's own — does this end-to-end. --- 🧠 How it works The agent calls tools; the server talks to the live EDS infrastructure. Read-only tools (content, sitemap, metadata) need no credentials at all. --- 🔑 One-click sign-in No more pasting a fresh admin token every day: > Use Chrome or Firefox — Safari blocks the local callback (same as Adobe's AEM CLI). EDS_API_KEY works as the CI / fallback path. --- 🛠️ The 41 tools Edge Delivery Services — publish, content, analytics **Publishing** - eds_preview_page - eds_publish_page - eds_unpublish_page - eds_preview_and_publish - eds_get_status - eds_purge_cache - eds_bulk_preview - eds_bulk_publish - eds_get_job_status **Content** - eds_get_page - eds_list_pages - eds_search_pages - eds_get_metadata - eds_get_sitemap - eds_get_redirects **Analytics & config** - eds_get_cwv - eds_get_404s - eds_get_experiments - eds_get_config - eds_get_logs - eds_get_api_keys Document Authoring (DA) — the authored *source*, not the rendered output Nine tools reach a site's Document Authoring source directly (admin.da.live), the source of truth behind an EDS site. Requires EDS_DA_TOKEN. **Read** - eds_da_list_sources - eds_da_get_source - eds_da_get_versions **Write** - eds_da_put_source - eds_da_delete_source - eds_da_copy_source - eds_da_move_source **Bulk ("clone") + safe writes** - eds_da_export - eds_da_push - eds_da_rollback > **eds_da_export / eds_da_push** bring the efficiency of aem content clone to agents: export a whole DA subtree in **one** call, operate on it, and push the batch back in **one** call — no local checkout, no aem-cli. Same model, network-native. > > **Safe by default.** eds_da_push takes dryRun: true to **preview** exactly what a bulk edit would do (create / update / unchanged, with line-diff counts) without writing a thing, and withUndo: true to make the write **reversible** — it returns an undo object you hand to eds_da_rollback to restore prior content and remove any docs the push created. Preview before writing, undo after: the difference between an impressive demo and something you'd point at a production site. > > EDS_DA_TOKEN is an Adobe IMS access token for Document Authoring — grab it from an authenticated da.live session (the IMS access_token). Document paths assume .html when no extension is given (index → index.html). Content audit — find what's wrong, before you fix it - eds_audit_page - eds_audit_site - eds_audit_report - eds_audit_snapshot - eds_audit_trend - eds_audit_monitor > **It tells you what's wrong.** eds_audit_site sweeps the whole site (or a subtree) and returns a **prioritized** list of issues across **SEO** (missing titles/descriptions, no H1, blocked from indexing), **accessibility** (images without alt text, missing landmarks, unlabeled form inputs), **freshness** (pages not updated in over a year), **sitemap coverage**, and — with a domain — **performance** (Core Web Vitals) and **404s** from Adobe's own real-user data. eds_audit_page does the same for one page. Read-only and safe to run anytime.