Aem Mcp Server
Operate Adobe Experience Manager content, components, and assets from natural-language agent commands during CMS integration work.
Overview
AEM MCP is a build-phase MCP server that connects your agent to Adobe Experience Manager for content, component, and asset operations over streamable-http.
What is this MCP server?
- Chat-driven operations against your AEM instance: content, components, and assets
- npm aem-mcp-server (registry v1.3.9) with streamable-http to local http://127.0.0.1:8502/mcp
- Bridges agents to Adobe Experience Manager workflows without bespoke scripts per task
- Maintained in easingthemes/aem-mcp-server on GitHub
- Targets teams already running AEM who want agent-assisted authoring and asset tasks
- Registry server version 1.3.9
- Transport: streamable-http at http://127.0.0.1:8502/mcp
- Documented operation areas: content, components, and assets
Community signal: 4 GitHub stars.
What problem does it solve?
AEM work is slow and UI-heavy when your agent cannot call your instance to inspect pages, components, or assets.
Who is it for?
Developers integrating or maintaining AEM who already have a reachable instance and want agent-assisted CMS tasks.
Skip if: Greenfield solo sites with no AEM license, or teams that forbid agent access to production CMS without human gates.
What do I get? / Deliverables
After you run the local MCP HTTP endpoint and register aem-mcp-server, your agent can perform AEM content and asset operations from chat-driven workflows.
- Agent-mediated AEM content, component, and asset operations
- Streamable-http MCP registration to local AEM bridge
- Faster iteration on CMS integration tasks from the IDE agent
Recommended MCP Servers
Journey fit
AEM connectivity is build-phase work when you integrate an enterprise site or headless content layer into your product. Integrations is the right shelf for instance-backed MCP tools that read and mutate CMS content alongside your app code.
How it compares
Enterprise CMS integration MCP, not a static site generator skill or generic headless CMS tutorial.
Common Questions / FAQ
Who is AEM MCP for?
Builders and integrators working on Adobe Experience Manager who want Claude Code, Cursor, or similar agents to drive content, component, and asset operations.
When should I use AEM MCP?
Use it in build when you are wiring or automating AEM-backed sites and need conversational access to your instance alongside code changes.
How do I add AEM MCP to my agent?
Install/configure the npm aem-mcp-server package and point your MCP client at the streamable-http URL http://127.0.0.1:8502/mcp with the local service running.