AEM MCP Server
Runtime environment used for executing the AEM MCP server
Package manager used for dependency management and running the server
Programming language used for server implementation
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 check the status of my AEM instance"
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 MCP Server
A Model Context Protocol (MCP) server for Adobe Experience Manager (AEM) local instance management. This server provides tools to interact with AEM instances, manage packages, check status, and perform common development tasks.
Features
The AEM MCP server provides the following tools:
1. aem_status
Check the status of an AEM instance including version, bundle count, and overall health.
Parameters:
host(optional): AEM host (default: localhost)port(optional): AEM port (default: 4502)username(optional): AEM username (default: admin)password(optional): AEM password (default: admin)
2. aem_install_package
Install a package (.zip file) in AEM.
Parameters:
packagePath(required): Path to the package file (.zip)host(optional): AEM host (default: localhost)port(optional): AEM port (default: 4502)username(optional): AEM username (default: admin)password(optional): AEM password (default: admin)force(optional): Force installation (default: false)
3. aem_list_packages
List all installed packages in AEM.
Parameters:
host(optional): AEM host (default: localhost)port(optional): AEM port (default: 4502)username(optional): AEM username (default: admin)password(optional): AEM password (default: admin)
4. aem_create_page
Create a new page in AEM.
Parameters:
parentPath(required): Parent path where to create the pagepageName(required): Name of the new pagepageTitle(required): Title of the new pagetemplate(required): Template path for the pagehost(optional): AEM host (default: localhost)port(optional): AEM port (default: 4502)username(optional): AEM username (default: admin)password(optional): AEM password (default: admin)
5. aem_replicate_content
Replicate content to publish instance (activate/deactivate).
Parameters:
path(required): Content path to replicateaction(optional): Replication action - 'activate' or 'deactivate' (default: activate)host(optional): AEM host (default: localhost)port(optional): AEM port (default: 4502)username(optional): AEM username (default: admin)password(optional): AEM password (default: admin)
6. aem_query_content
Query content using JCR-SQL2 or XPath.
Parameters:
query(required): Query string (JCR-SQL2 or XPath)type(optional): Query type - 'JCR-SQL2' or 'xpath' (default: JCR-SQL2)limit(optional): Maximum number of results (default: 20)host(optional): AEM host (default: localhost)port(optional): AEM port (default: 4502)username(optional): AEM username (default: admin)password(optional): AEM password (default: admin)
7. aem_bundle_status
Check OSGi bundle status.
Parameters:
bundleId(optional): Specific bundle ID or symbolic namehost(optional): AEM host (default: localhost)port(optional): AEM port (default: 4502)username(optional): AEM username (default: admin)password(optional): AEM password (default: admin)
8. aem_clear_cache
Clear various AEM caches.
Parameters:
cacheType(optional): Type of cache to clear - 'dispatcher', 'clientlibs', or 'all' (default: all)host(optional): AEM host (default: localhost)port(optional): AEM port (default: 4502)username(optional): AEM username (default: admin)password(optional): AEM password (default: admin)
Related MCP server: Expo MCP Server
Installation
Clone or download this repository
Install dependencies:
npm installBuild the project:
npm run build
Usage
Running the Server
npm startDevelopment Mode
npm run devConfiguration
The server uses default AEM credentials (admin/admin) and connects to localhost:4502 by default. You can override these settings by providing different parameters when calling the tools.
Example Usage
Once the MCP server is configured and running, you can use the tools through your MCP client:
Check AEM status:
aem_statusInstall a package:
aem_install_packagewithpackagePath: "/path/to/package.zip"Create a page:
aem_create_pagewith required parametersQuery content:
aem_query_contentwithquery: "SELECT * FROM [cq:Page]"
Requirements
Node.js 18+
TypeScript
Running AEM instance (local or remote)
Appropriate AEM credentials
License
MIT License
Available Tools
8 toolsaem_bundle_statusC
Check OSGi bundle status
Inputs: bundleId, host, port, username, +1 more.
aem_clear_cacheC
Clear various AEM caches
Inputs: cacheType, host, port, username, +1 more.
aem_create_pageC
Create a new page in AEM
Inputs: parentPath (required), pageName (required), pageTitle (required), template (required), +4 more.
aem_install_packageC
Install a package in AEM
Inputs: packagePath (required), host, port, username, +2 more.
aem_list_packagesB
List installed packages in AEM
Inputs: host, port, username, password.
aem_query_contentC
Query content using JCR-SQL2 or XPath
Inputs: query (required), type, limit, host, +3 more.
aem_replicate_contentC
Replicate content to publish instance
Inputs: path (required), action, host, port, +2 more.
aem_statusC
Check the status of AEM instance
Inputs: host, port, username, password.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose targeting specific AEM operations: bundle status, cache clearing, page creation, package installation, package listing, content querying, content replication, and instance status. There is no overlap in functionality, making tool selection straightforward for an agent.
All tools follow a consistent 'aem_verb_noun' pattern with snake_case throughout, such as aem_clear_cache and aem_create_page. This predictable naming scheme enhances readability and reduces cognitive load for agents.
With 8 tools, the server is well-scoped for AEM administration tasks, covering key operations like instance management, content handling, and package control. Each tool earns its place without being overwhelming or insufficient for the domain.
The toolset provides strong coverage for core AEM workflows, including instance status, content creation/querying/replication, and package management. Minor gaps exist, such as the lack of tools for updating or deleting pages/packages, but agents can likely work around these with existing tools.
Maintenance
Related MCP Connectors
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.
A Model Context Protocol server for Wix AI tools
MCP Server for JFrog, providing tools for development and artifact management.
Related MCP Servers
- AlicenseBqualityFmaintenanceA Model Context Protocol server that provides tools for code modification and generation via Large Language Models, allowing users to create, modify, rewrite, and delete files using structured XML instructions.122MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that provides development and debugging tools for Expo-based React Native applications, enabling developers to manage Expo servers, capture logs, and manipulate project files.51MIT
- AlicenseCqualityCmaintenanceA Model Context Protocol server for Adobe Experience Manager that provides REST/JSON-RPC APIs for content, component, and asset management with AI, chatbot, and automation integrations.4814AGPL 3.0
- AlicenseAqualityCmaintenanceA Model Context Protocol server that provides tooling support for Ember.js development, allowing developers to execute CLI commands, run codemods, access documentation, and discover community resources.7569 npm28MIT