AEM DEV MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AEM_INSTANCES_CONFIG_PATH | No | Path to AEM instances configuration file | ~/aem-instances.yaml |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| aem_health_checkA | Performs comprehensive health checks on AEM instances including memory, threads, bundles, requests, and repository metrics. Either aliases or instances must be provided. |
| aem_groovy_executeB | Execute Groovy scripts on AEM instances via Groovy Console for maintenance and automation tasks |
| aem_bundle_listB | List OSGi bundles from AEM instances |
| aem_bundle_startC | Start OSGi bundles on AEM instances |
| aem_bundle_stopB | Stop OSGi bundles on AEM instances |
| aem_bundle_refreshC | Refresh OSGi bundles on AEM instances |
| aem_bundle_uninstallB | Uninstall OSGi bundles on AEM instances |
| aem_bundle_restartC | Restart OSGi bundles on AEM instances |
| aem_bundle_detailsB | Get detailed information about OSGi bundles from AEM instances |
| aem_component_listB | List OSGi components from AEM instances with optional state and name filtering |
| aem_component_enableB | Enable OSGi components on AEM instances by component name |
| aem_component_disableB | Disable OSGi components on AEM instances by component name |
| aem_component_detailsB | Get detailed information about a specific OSGi component by name |
| aem_configuration_listB | List OSGi configurations from AEM instances |
| aem_configuration_getC | Get a specific OSGi configuration |
| aem_configuration_createB | Create a new OSGi configuration |
| aem_configuration_updateC | Update an existing OSGi configuration |
| aem_configuration_deleteC | Delete an OSGi configuration |
| aem_configuration_unbindC | Unbind an OSGi configuration from a bundle |
| aem_logs_searchA | Search AEM logs with regex patterns across different log types and navigate through paginated results |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 20 tools
Tools are clearly grouped by resource (bundles, components, configurations) with action-specific verbs, making most selections straightforward. The only mild ambiguities are bundle_refresh vs bundle_restart and the similar lifecycle actions across different resource types.
The server follows a consistent aem_<resource>_<action> pattern with snake_case throughout. Minor inconsistencies like aem_bundle_details vs aem_configuration_get and aem_logs_search vs singular resource prefixes slightly break the uniformity.
At 20 tools, the set is on the heavier side, especially when compared to typical MCP servers. However, the count is justified by the broad AEM OSGi administration scope covering bundles, components, configurations, logs, health, and Groovy scripting.
The tool surface covers most lifecycle operations for OSGi bundles, components, and configurations, along with logs, health checks, and Groovy execution. Notable gaps include bundle install/upload and package management, but existing tools cover the core development workflows well.