Skip to main content
Glama
arkadiusz-rosiak

AEM DEV MCP Server

by arkadiusz-rosiak
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to AEM DEV MCP Server

No user-submitted related servers found.

    Related Servers

    • AEM MCP Server

      udaykumarbpatel
      A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive Model Context Protocol server for Adobe Experience Manager that provides 35+ REST/JSON-RPC API methods for complete content, component, asset, and template management. Enables AI-powered AEM automation through natural language interfaces with support for page operations, component CRUD, asset management, and publishing workflows.
      MIT

    • Tomcat MCP

      sarath-451
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI-assisted management of Apache Tomcat, including start/stop, WAR deployment, log analysis, thread and heap dumps, and diagnostics.
      21 npm
      MIT

    • AEM Assets MCP Server

      SatoshiInoue
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables interaction with Adobe Experience Manager (AEM) Assets through the Author API. It allows users to browse folders, search for assets, retrieve detailed asset information, and perform bulk metadata updates using natural language.
      1
      -

    • Mistral Agent Manager

      Uzbyr
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables management of Mistral AI agents through MCP tools including creating, listing, searching, viewing details, and deleting agents. Integrates with Mistral API to provide agent management capabilities through natural language interactions.
      1
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 20 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources