AEM Block Collection MCP Server
# 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.
## Installation
```bash
npm install
```
## Usage
```bash
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:
```json
{
"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.
TDQS
Scored across 1 tool
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.
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.
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.
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.