Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@AEM Block Collection MCP Server list all available AEM blocks"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A minimal MCP (Model Context Protocol) server that provides access to AEM block metadata from blocks.json.
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: Markdown Sidecar MCP Server
npm installnode index.jsThe server automatically looks for blocks.json in the current directory or parent directories.
list_blocksLists 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.
@modelcontextprotocol/sdk - MCP server implementation
fs-extra - Enhanced file system operations
zod - Schema validation
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.
List all available AEM blocks with metadata from blocks.json
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the source ('blocks.json') and output includes metadata, but fails to describe key behaviors like whether this is a read-only operation, potential performance impacts, error handling, or format of the returned data. This leaves significant gaps for an agent to understand how the tool behaves.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that front-loads the key information ('List all available AEM blocks') and adds necessary detail ('with metadata from blocks.json') without any wasted words. It's appropriately sized for a simple tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It states the purpose and source, but lacks details on behavioral traits and output format, which are important for an agent to use it correctly. It meets the basic requirement but has clear gaps in completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and a baseline of 4 is appropriate as it doesn't mislead or omit parameter information.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('List') and resource ('AEM blocks'), and specifies the source ('blocks.json') and what's included ('with metadata'). It's specific about what the tool does, though without sibling tools to differentiate from, it can't achieve a perfect 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool, such as prerequisites, context, or alternatives. It simply states what the tool does without indicating any usage scenarios or constraints.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.0.0list_blocksWith 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.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Public read-only MCP for products, frameworks, guides, methodology, and blog metadata.
Access and maintain design system docs, tokens, components, skills, and contexts across any project.
Software component catalog: search your org's services, docs, APIs, dependencies, and ownership.
Read-only MCP for Electrik Slate: Blade component docs, blocks gallery, source, and llms.txt.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ACSGenUI/mcp-block-collection'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
