One AEM MCP Server to Rule Them All

AEM spans many products and APIs — sites, assets, Dynamic Media, Content Hub, forms, translation. How do you give an AI agent one coherent way into all of it? Our answer is a single AEM MCP server.

The first version wrapped every endpoint in its own tool — 69 of them — until the LLM's context window buckled under the weight. This session walks through how we collapsed that surface into four generic tools, backed by curated knowledge files and composable recipes that teach the model not just what the API offers, but how to use it. Those same four tools now front the full AEM surface — hundreds of operations across every domain — from one MCP server, with no per-product tooling to maintain.

We'll cover the architecture, the safety guarantees around reads and writes, and the lessons from running this in production. The pattern generalizes to any OpenAPI-described system, not just AEM.