AEM Block Collection MCP Server
Related Servers
Alternatives to AEM Block Collection MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceA read-only MCP server that provides verified WordPress block definitions and markup across product environments, enabling search, comparison, generation, and validation of blocks.-
- AlicenseNot gradedqualityDmaintenanceProvides access to markdown documentation for local NPM, Go, and PyPi packages as MCP resources or tools. It enables informed code generation by surfacing documentation directly from a project's working directory.MIT
- AlicenseAqualityBmaintenanceExposes design system component documentation to LLM clients via MCP, allowing listing and retrieving component contexts from Markdown files with YAML frontmatter.25 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to read and analyze local Storybook component specifications, including component listings, props, and source code examples.3 npmISC
- FlicenseBqualityFmaintenanceEnables AI assistants to search documentation, read and update configuration files, and discover settings across your development workspace. Supports JSON, YAML, TOML, and Markdown files with seamless integration for GitHub Copilot and other MCP clients.5-
- FlicenseBqualityBmaintenanceProvides AI assistants with structured access to Unity project metadata, build settings, and agent documentation directly from the filesystem. It enables querying project details and scene configurations without requiring the Unity Editor to be running.10046 npm5-
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.