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

    • 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.
      40 npm
      MIT

    • 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
      -

    • connect-to-server-mcp

      vstlmkh
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to securely connect to and manage remote servers via SSH, with tools for running commands, file operations, log inspection, service management, and system monitoring under configurable access controls and audit logging.
      12
      15 npm
      1
      MIT

    • Hybris MCP Server

      Emenowicz
      A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to interact with SAP Commerce Cloud (Hybris) instances for product management, order viewing, FlexibleSearch queries, Groovy script execution, ImpEx operations, and system administration tasks.
      16
      13
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    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