EDS MCP Server
Related Servers
Alternatives to EDS MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that supercharges AEM Edge Delivery Services development in IDEs by providing tools for scaffolding blocks, validating code, and generating configurations directly through natural language.MIT
- -licenseBqualityNot gradedmaintenanceMCP server for Akamai APIs. 198 tools covering Property Manager, Edge DNS, CPS, WAF, and reporting. Built with TypeScript, featuring modular architecture, comprehensive testing, and multi-account support. Make Akamai accessible to AI assistants.19 npm10-
- AlicenseNot gradedqualityDmaintenanceA comprehensive Model Context Protocol server for Adobe Experience Manager that provides 35+ REST/JSON-RPC API methods for complete content, component, asset, and template management. Enables AI-powered AEM automation through natural language interfaces with support for page operations, component CRUD, asset management, and publishing workflows.MIT
- AlicenseNot gradedqualityAmaintenanceThe first full-featured MCP server for Adobe Experience Platform: 29 tools across schemas, datasets, profiles, segments, query service, and GDPR/CCPA privacy operations. Extends Adobe's read-only beta with production-grade write operations.131 npmApache 2.0
- AlicenseCqualityDmaintenanceA SitecoreMCP version that can be used in enterprises100385 npmApache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables Adobe Experience Platform and AEM content operations through a shared tool registry, exposing health checks, fragment search, sandbox management, dataset queries, and content fragment fetching via MCP and web interfaces.-
TDQS
Scored across 41 tools
Most tools separate cleanly by resource and action, and the consistent prefixing/describing makes preview, publish, DA source, audit, and fix workflows mostly distinct. Some confusion is possible between eds_audit_site, eds_audit_report, and eds_audit_snapshot, which all run the same audit with different outputs, and eds_preview_and_publish duplicates a two-step workflow.
Names generally follow an eds_<domain>_<action>_<object> pattern, and the eds_da_* and eds_audit_* grouping is easy to recognize. Minor deviations like eds_preview_and_publish and eds_audit_report break the verb-first convention, but there is no chaotic mixing of styles.
41 tools is beyond the threshold where a tool set starts to feel bloated, even for a fairly broad EDS management domain. Several audit/reporting variants and single-purpose helpers could be consolidated without losing capability.
The tool set covers the main EDS lifecycle very well: page preview/publish/unpublish, CDN cache, DA source CRUD plus move/copy/versions/export/push/rollback, and a full audit-to-fix path. Peripheral gaps exist, such as API key creation/deletion and config editing, but they are not central to the server's apparent purpose.