Skip to main content
Glama
AEM Block Collection MCP Server
by ACSGenUI

AEM Block Collection MCP Server

A minimal MCP (Model Context Protocol) server that provides access to AEM block metadata from blocks.json.

What it does

This server exposes a single tool: list_blocks - which reads AEM block information from a blocks.json file and returns structured data about all available blocks.

Related MCP server: WordPress Block Catalog MCP

Installation

npm install

Usage

node index.js

Configuration

The server automatically looks for blocks.json in the current directory or parent directories.

MCP Tool

list_blocks

Lists all available AEM blocks with metadata from blocks.json.

Input: None required Output: JSON with block information including names, descriptions, file paths, and file counts.

Dependencies

  • @modelcontextprotocol/sdk - MCP server implementation

  • fs-extra - Enhanced file system operations

  • zod - Schema validation

MCP Configuration

To use this server with an MCP client (like Claude Desktop or Cline), add this configuration:

{
  "mcpServers": {
    "aem-block-collection": {
      "command": "node",
      "args": ["https://github.com/ACSGenUI/mcp-block-collection#main"],
      "env": {}
    }
  }
}

Note: Replace https://github.com/ACSGenUI/mcp-block-collection with the actual node module name of the server.

Available Tools

1 tool
list_blocksList AEM BlocksB

List all available AEM blocks with metadata from blocks.json

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'list_blocks' has a clear and distinct purpose that cannot be confused with any other tool in this set.

    Naming Consistency5/5

    The single tool name 'list_blocks' follows a clear verb_noun pattern. Since there is only one tool, consistency is inherently perfect with no deviations or mixed conventions to evaluate.

    Tool Count2/5

    A single tool is too few for a server with 'Collection' in its name, suggesting it should manage AEM blocks. This minimal surface lacks essential operations like create, update, delete, or get specific blocks, severely limiting functionality for the apparent domain.

    Completeness1/5

    The tool set is severely incomplete for managing AEM blocks. It only provides listing functionality, missing all CRUD operations (create, read, update, delete) and other lifecycle actions. This will cause significant agent failures when trying to perform basic block management tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables users to decompose raw prompts into structured typed blocks, edit or craft block JSON, and compile them into Claude-optimized XML prompts directly within Claude Code. It also exposes the available block types and recommended ordering for prompt construction.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables users to decompose raw prompts into structured typed blocks, edit them as JSON, and compile them into Claude-optimized XML prompts, with tools for listing available block types.
      -