AEM MCP Server
This server is an MCP gateway that lets AI/IDE clients manage Adobe Experience Manager 6.5 Author content, components, assets, workflows, and versions over stdio or HTTP.
Component management: validate, create, update, delete, bulk-update, and undo component changes
Page/content operations: scan and list pages, create/delete pages, retrieve page content, text, images, and properties
Site/locale handling: fetch sites, language masters, available locales, and replicate/publish content to selected locales
Search & query: page search, Query Builder search, JCR queries, and legacy node exploration
Asset management: upload, update, delete assets, and update image paths with verification
Workflow control: start, get status, list active, complete steps, suspend, resume, cancel workflows, and list workflow models
Versioning: get history, create, restore, compare, and delete versions
Templates: list templates and inspect template structure
Content extraction: retrieve all text, images, Experience Fragments, and Content Fragments from a page
Transports: MCP stdio for IDE clients plus optional Streamable HTTP with API key/Basic auth, health endpoints, and convenience REST methods
Uses environment variables through .env files for configuration of AEM connections, API keys, and server settings
Built on Node.js runtime (v18+) for server operations and AEM connectivity
Integrates with Ollama to provide local LLM capabilities for natural language AEM management
Connects to OpenAI's API to enable natural language processing for AEM content management tasks
Features a Telegram bot for conversational AEM management, allowing chat-based content and component operations
Built with TypeScript for type-safe development and modern JavaScript features
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@AEM MCP Server create a new page in the marketing site using the article template"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
AEM 6.5 MCP Server
Standalone Node.js Model Context Protocol server for Adobe Experience Manager 6.5 Author. It does not install anything on AEM.
Status: pre-production. Use the capability matrix as the list of supported operations. Release gates are in docs/adr/0001-standalone-http-mcp.md.
This project is AGPL-3.0 for open source use. Commercial licensing is described in COMMERCIAL_LICENSE.md.
AEMaaCS is a different product: see aemaacs-mcp-server. AEM 6.5 LTS is out of scope.
What this is
MCP stdio for IDE clients (primary).
Optional MCP Streamable HTTP (
POST /mcp) with API key or HTTP Basic. OAuth is out of scope.One typed tool catalog driving both transports.
Documented AEM 6.5 HTTP only: Granite CSRF,
/bin/wcmcommand,/bin/replicate.json, QueryBuilder, Assetscreateasset.html, Workflow REST.
Related MCP server: SupaUI MCP Server
What this is not
Production-ready until CI gates and live Author contract tests pass.
An AEM package, OSGi service, or RepoInit installer.
Atomic bulk rollback, JCR-SQL2, MSM rollout, tree activation, or
.infinity.jsondumps.An OpenAI/Anthropic/Telegram bot.
Requirements
Node.js 20 or 22
AEM 6.5 Author SP17+ reachable over HTTP(S)
A technical user that already exists in AEM User Admin (ACL checklist)
Quick start (stdio)
cp .env.example .env
# set AEM_HOST, AEM_SERVICE_USER, AEM_SERVICE_PASSWORD
npm ci
npm run build
npm run mcpCursor / Claude desktop config:
{
"mcpServers": {
"aem-65": {
"command": "node",
"args": ["/absolute/path/to/dist/mcp/stdio.js"],
"env": {
"AEM_HOST": "http://localhost:4502",
"AEM_SERVICE_USER": "mcp-technical",
"AEM_SERVICE_PASSWORD": "<secret>"
}
}
}
}Optional HTTP gateway
export MCP_API_KEY=replace-me
export HTTP_ENABLED=true
npm startLiveness (no auth):
GET /health/liveReadiness (auth):
GET /health/readyMCP:
POST /mcp(SDK Streamable HTTP)Convenience REST:
GET /api/methods,POST /api/methods/:name(same auth; not a substitute for MCP)
Put TLS in front. Bind HOST=127.0.0.1. Set ALLOWED_HOSTS and CORS_ORIGINS.
curl -sS -H "X-API-Key: $MCP_API_KEY" http://127.0.0.1:3001/api/methodsConfiguration
See .env.example. Required: AEM_HOST, AEM_SERVICE_USER, AEM_SERVICE_PASSWORD. Production/staging refuse admin/admin and refuse HTTP without API key or Basic.
Default page resource type is core/wcm/components/page/v3/page. Override with AEM_DEFAULT_PAGE_RESOURCE_TYPE and AEM_DEFAULT_CONTAINER for your project.
Architecture
MCP client → stdio or Streamable HTTP → typed tool catalog
→ validation / path policy / audit → AEM 6.5 HTTP adapter → AuthorDetails: capability matrix, tool reference, operations, threat model, 1.x migration.
Development
npm ci
npm run lint
npm test
npm run buildLive Author tests (optional): AEM_INTEGRATION=1 npm test.
License
AGPL-3.0-or-later. Contact via LinkedIn for commercial licensing.
Available Tools
48 toolsactivatePageC
Activate (publish) a single page
Inputs: pagePath (required), activateTree.
bulkUpdateComponentsA
Update multiple components in a single operation with validation and rollback support
Inputs: updates (required), validateFirst, continueOnError.
cancelWorkflowC
Cancel a workflow instance
Inputs: workflowId (required), reason.
compareVersionsC
Compare two versions of content
Inputs: path (required), version1 (required), version2 (required).
completeWorkflowStepD
Complete a workflow step
Inputs: workflowId (required), stepName (required), comment.
createComponentC
Create a new component on a page
Inputs: pagePath (required), componentType (required), resourceType (required), properties, +1 more.
createPageC
Create a new page in AEM
Inputs: parentPath (required), title (required), template (required), name, +1 more.
createVersionC
Create a new version of content
Inputs: path (required), label, comment.
deactivatePageC
Deactivate (unpublish) a single page
Inputs: pagePath (required), deactivateTree.
deleteAssetC
Delete an asset from AEM DAM
Inputs: assetPath (required), force.
deleteComponentC
Delete a component from AEM
Inputs: componentPath (required), force.
deletePageC
Delete a page from AEM
Inputs: pagePath (required), force.
deleteVersionD
Delete a specific version
Inputs: path (required), versionName (required).
enhancedPageSearchC
Intelligent page search with comprehensive fallback strategies and cross-section search
Inputs: searchTerm (required), basePath (required), includeAlternateLocales.
executeJCRQueryD
Execute JCR query
Inputs: query (required), limit.
fetchAvailableLocalesC
Get available locales for a site and language master
Inputs: site (required), languageMasterPath (required).
fetchLanguageMastersC
Get language masters for a specific site
Inputs: site (required).
fetchSitesB
Get all available sites in AEM
Inputs: no named parameters.
getAllTextContentC
Get all text content from a page including titles, text components, and descriptions
Inputs: pagePath (required).
getAssetMetadataD
Get asset metadata
Inputs: assetPath (required).
getNodeContentD
Legacy: Get JCR node content
Inputs: path (required), depth.
getPageContentC
Get all content from a page including Experience Fragments and Content Fragments
Inputs: pagePath (required).
getPageImagesC
Get all images from a page, including those within Experience Fragments
Inputs: pagePath (required).
getPagePropertiesD
Get page properties
Inputs: pagePath (required).
getPageTextContentC
Get text content from a specific page
Inputs: pagePath (required).
getStatusC
Get workflow status by ID
Inputs: workflowId (required).
getTemplatesC
Get available page templates
Inputs: sitePath.
getTemplateStructureC
Get detailed structure of a specific template
Inputs: templatePath (required).
getVersionHistoryC
Get version history for a content path
Inputs: path (required).
getWorkflowModelsB
Get all available workflow models
Inputs: no named parameters.
listActiveWorkflowsC
List all currently running workflow instances
Inputs: limit.
listChildrenD
Legacy: List child nodes
Inputs: path (required).
listMethodsB
Get list of available MCP methods
Inputs: no named parameters.
listPagesC
List all pages under a site root
Inputs: siteRoot, depth, limit.
replicateAndPublishC
Replicate and publish content to selected locales
Inputs: selectedLocales (required), componentData (required), localizedOverrides.
restoreVersionC
Restore content to a specific version
Inputs: path (required), versionName (required).
resumeWorkflowB
Resume a suspended workflow instance
Inputs: workflowId (required).
scanPageComponentsC
Scan a page to discover all components and their properties
Inputs: pagePath (required).
searchContentC
Search content using Query Builder
Inputs: type, fulltext, path, limit.
startWorkflowC
Start a new workflow instance
Inputs: model (required), payloadPath (required), title, comment.
suspendWorkflowC
Suspend a workflow instance
Inputs: workflowId (required), reason.
undoChangesC
Undo the last component changes
Inputs: jobId (required).
unpublishContentC
Unpublish content from the publish environment
Inputs: contentPaths (required), unpublishTree.
updateAssetC
Update an existing asset in AEM DAM
Inputs: assetPath (required), metadata, fileContent, mimeType.
updateComponentC
Update component properties in AEM
Inputs: componentPath (required), properties (required).
updateImagePathC
Update the image path for an image component and verify the update
Inputs: componentPath (required), newImagePath (required).
uploadAssetC
Upload a new asset to AEM DAM
Inputs: parentPath (required), fileName (required), fileContent (required), mimeType, +1 more.
validateComponentC
Validate component changes before applying them
Inputs: locale (required), pagePath (required), component (required), props (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 48 tools
Most tools have distinct purposes targeting specific AEM operations like page management, asset handling, workflow control, and versioning. However, some overlap exists between 'getPageContent' and 'getAllTextContent'/'getPageTextContent', and between 'listPages' and 'enhancedPageSearch', which could cause minor confusion for agents.
The naming follows a consistent verb_noun pattern throughout (e.g., 'activatePage', 'createComponent', 'getAssetMetadata'), with clear action-object pairs. Minor deviations like 'enhancedPageSearch' (adjective-verb-noun) and 'listMethods' (which doesn't fit the AEM domain) slightly break the pattern but overall maintain good readability.
With 48 tools, the count is excessive for typical MCP server scope, likely overwhelming for agents and increasing complexity. While AEM is a complex system, this many tools suggests poor scoping or fragmentation, as many operations could be consolidated into fewer, more general tools.
The tool set provides comprehensive coverage for AEM content management, including full CRUD operations for pages, components, assets, and versions, plus workflow management, search, and validation. No obvious gaps exist; agents can perform end-to-end tasks without dead ends in this domain.
Maintenance
Related MCP Connectors
A Model Context Protocol server for Wix AI tools
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
Related MCP Servers
- AlicenseAqualityBmaintenanceA Model Context Protocol server that enables AI assistants to interact with Strapi CMS instances through a standardized interface, supporting content types and REST API operations.569 npm75MIT
- AlicenseCqualityCmaintenanceA Model Context Protocol server that enables AI agents to generate, fetch, and manage UI components through natural language interactions.37ISC
- AlicenseBqualityDmaintenanceA Model Context Protocol server that provides tools to interact with Adobe Experience Manager instances, allowing users to manage packages, check status, create pages, replicate content, and perform other common AEM development tasks.8512 npmAGPL 3.0
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI models to interact with Mobi instances, providing structured data exchange and command execution for ontology management, data retrieval, and content creation.2MIT