Skip to main content
Glama
pradeep-moolemane

AEM MCP Server

by pradeep-moolemane
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to AEM 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

    • Expo MCP Server

      mattlemmone
      F
      license
      B
      quality
      D
      maintenance
      A 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.
      5
      1
      -

    • mcp-server-code-assist

      abhishekbhakat
      A
      license
      B
      quality
      F
      maintenance
      A 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.
      12
      2
      MIT

    • Ember MCP Server

      ember-tooling
      A
      license
      A
      quality
      B
      maintenance
      A 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.
      7
      203 npm
      28
      MIT
    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.4/5.0

    Scored across 8 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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

    ActivityInactive
    ResponsivenessNo issues

    Resources