{"id":80539,"date":"2026-07-08T21:35:22","date_gmt":"2026-07-08T16:05:22","guid":{"rendered":"https:\/\/www.tothenew.com\/blog\/?p=80539"},"modified":"2026-07-17T07:51:58","modified_gmt":"2026-07-17T02:21:58","slug":"adobe-and-gen-ai-part-2-local-mcp-servers-for-aem-development","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/adobe-and-gen-ai-part-2-local-mcp-servers-for-aem-development\/","title":{"rendered":"Adobe and Gen AI \u2013 Part 2: Local MCP Servers for AEM Development"},"content":{"rendered":"

Introduction<\/h2>\n

In Part 1<\/a> of this series, we looked at Adobe Skills. Skills teach AI coding assistants Adobe’s recommended way of doing things.<\/p>\n

Skills tell the assistant how to do something. But on their own, they do not know what is happening in your running AEM instance right now. They do not know which bundle is stuck, what the last few requests looked like, or why a page is not caching. That is where Model Context Protocol (MCP) comes in.<\/p>\n

In this part, we will look at how Adobe uses MCP to give AI coding assistants, like Cursor and Claude Code, live visibility into your local AEM and Dispatcher environments.<\/p>\n

 <\/p>\n

AEM Quickstart MCP Server<\/h2>\n

MCP, or Model Context Protocol, is an open standard that lets an AI assistant talk to external tools and services. Instead of relying only on the chat history or the file open in your editor, the assistant can call a tool and pull in real information: log entries, running service status, API responses, config files. This is the same thing a developer would do by checking a log file or hitting an endpoint. The assistant just does it as part of answering your question.<\/p>\n

\"generic-mcp-architecture\"<\/p>\n

Adobe provides an MCP server for local AEM SDK (Valid for AEM as a cloud) development. Once it is connected, your AI assistant can look directly at your running Author or Publish instance, instead of relying only on the code you paste into the chat.<\/p>\n

Prerequisites<\/h3>\n