npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

aem-mcp-server

v1.6.2

Published

AEM MCP server. Chat with your AEM instance for content, component, and asset operations.

Readme

AEM MCP Server (aem-mcp-server)

Version Release Status CodeQL Analysis semver: semantic-release AGPL-3.0

AEM MCP Server is a full-featured Model Context Protocol (MCP) server for Adobe Experience Manager (AEM). It provides a simple integration with any AI Agent. This project is designed for non-technical persons who want to manage AEM via natural language.


Overview

  • Manage your AEM instance with natural language — content, components, assets, workflows
  • Works with any MCP-compatible client:
    • AI IDEs — Cursor, VS Code + Copilot, Windsurf, Cline, JetBrains AI Assistant, Zed
    • CLI agents — Claude Code, GitHub Copilot CLI, Gemini CLI, Amazon Q CLI
    • Chat & desktop apps — Claude Desktop, ChatGPT Desktop, Goose
  • Supports both AEMaaCS and self-hosted AEM instances
  • Two transport modes — stdio via npx (recommended, zero install) and streamable HTTP

Quick Start

Prerequisites

  • Node.js 20.19.0+ || 22.12.0+ || 23+
  • Access to an AEM instance (local or remote)

Stdio Transport (recommended)

No installation needed — the AI agent downloads and spawns the process automatically via npx.

Add to your project's MCP config (.mcp.json, .vscode/mcp.json, .cursor/mcp.json, etc.):

{
  "mcpServers": {
    "AEM": {
      "command": "npx",
      "args": ["-y", "aem-mcp-server", "-t", "stdio", "-H", "http://localhost:4502", "-u", "admin", "-p", "admin"]
    }
  }
}

Secrets: Since MCP config files are typically committed to the repo, avoid hardcoding credentials. Use your client's env var syntax instead:

| Client | Syntax | |---|---| | Claude Code (.mcp.json) | ${AEM_PASSWORD} or ${AEM_PASSWORD:-admin} | | VS Code / Copilot | ${input:aem-password} (prompts securely) or envFile | | Cursor | ${env:AEM_PASSWORD} |

Example with env var references (Claude Code):

{
  "mcpServers": {
    "AEM": {
      "command": "npx",
      "args": ["-y", "aem-mcp-server", "-t", "stdio", "-H", "${AEM_HOST:-http://localhost:4502}", "-u", "${AEM_USER:-admin}", "-p", "${AEM_PASSWORD:-admin}"]
    }
  }
}

Streamable HTTP Transport (alternative)

For scenarios where you need a persistent server (shared team server, multiple clients connecting simultaneously, etc.), install globally and start the server manually:

npm install aem-mcp-server -g
aem-mcp -H=http://localhost:4502 -u=admin -p=admin

Then point your AI agent to the URL:

{
  "mcpServers": {
    "AEM": {
      "url": "http://127.0.0.1:8502/mcp"
    }
  }
}

Install MCP Server

Configuration

Options:
      --version    Show version number                                 [boolean]
  -H, --host                         [string] [default: "http://localhost:4502"]
  -u, --user                                         [string] [default: "admin"]
  -p, --pass                                         [string] [default: "admin"]
  -i, --id         clientId                               [string] [default: ""]
  -s, --secret     clientSecret                           [string] [default: ""]
  -m, --mcpPort                                         [number] [default: 8502]
  -t, --transport  Transport mode: http (default) or stdio
                           [string] [choices: "http", "stdio"] [default: "http"]
  -I, --instances  Named AEM instances: "local:http://localhost:4502:admin:admin
                   ,qa:https://qa.example.com:user:pass"  [string] [default: ""]
  -h, --help       Show help                                           [boolean]

Authentication:

  • For AEMaaCS, use clientId and clientSecret for OAuth S2S authentication. More info.
  • For self-hosted AEM, use user/pass. Default credentials are admin:admin.

Multi-instance: Connect to multiple AEM instances simultaneously:

aem-mcp --instances "author:http://localhost:4502:admin:admin,publish:http://localhost:4503:admin:admin"

All tools will get an instance parameter to target a specific instance.


Features

  • 57 MCP Tools covering pages, components, assets, workflows, content fragments, and experience fragments
  • MCP Resources — agents discover components, sites, templates, and workflow models upfront via resources/list, eliminating discovery roundtrips
  • Tool Annotations — every tool tagged with group, readOnly, and complexity so agents can make smarter tool selection decisions
  • Response Verbosityverbosity parameter (summary/standard/full) on content-reading tools strips JCR internals and truncates long text
  • Actionable Errors — error responses include suggestion and alternatives fields for self-healing agent workflows
  • Component Operations: Update, scan, add, convert, and bulk-manage AEM components (including Experience Fragments)
  • Content & Experience Fragments: Full CRUD + variation management for both CF and XF
  • Advanced Search: QueryBuilder, fulltext, fuzzy, and enhanced page search
  • Replication & Workflows: Publish/unpublish content, start/advance/delegate workflow stages
  • Text & Image Extraction: Extract all text and images from pages, including fragments
  • Template & Structure Discovery: List templates, analyze page/component structure
  • Multi-instance: Connect to multiple AEM instances simultaneously; tools and resources are instance-aware
  • Security: Basic auth and OAuth S2S, environment-based config, safe operation defaults

Usage

Once configured in your AI IDE, just ask in natural language:

List all components on MyPage

MCP Resources

The server exposes read-only MCP resources so agents can discover AEM catalogs without tool calls:

| Resource URI | Description | |---|---| | aem://{instance}/components | All components (name, resourceType, title, group) | | aem://{instance}/sites | Site roots and language structure under /content | | aem://{instance}/templates | Available page templates (path, title) | | aem://{instance}/workflow-models | Workflow models (ID, title, description) |

Resources return summary data only. In multi-instance mode, each instance gets its own set of resource URIs.

API Documentation

For detailed API documentation, please refer to the API Docs.

Similar Projects

  1. https://github.com/easingthemes/aem-mcp-server (Used as a base for this project)
  2. https://github.com/indrasishbanerjee/aem-mcp-server (Used as a base for #1)
  3. https://www.npmjs.com/package/@myea/aem-mcp-handler (Looks like an original source of #2)