AEM Block Collection MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_blocksB | List all available AEM blocks with metadata from blocks.json |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| aem-blocks-metadata | Access to the complete blocks.json metadata for AEM blocks |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.