A
licenseB
qualityD
maintenanceA Model Context Protocol (MCP) compliant server that allows Large Language Models (LLMs) to search and retrieve content from microCMS APIs.
2
MIT
microCMS MCP Server
by microcmsio
Related Servers
Alternatives to microCMS MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceA Model Context Protocol server that enables Claude and other AI assistants to access and update Kintone data through natural language commands, supporting operations like record management, file handling, app administration, and space collaboration.7911AGPL 3.0
- AlicenseCqualityDmaintenanceA Model Context Protocol server that enables Claude to interact directly with Contentful CMS, allowing the AI to fetch content types and entries from a Contentful space.22MIT
- AlicenseAqualityCmaintenanceA Model Context Protocol server that enables AI assistants to interact with Strapi CMS instances through a standardized interface, supporting content types and REST API operations.56975MIT
Contentfulofficial
AlicenseNot gradedqualityAmaintenanceA Model Context Protocol (MCP) server that provides AI assistants with comprehensive tools to interact with Contentful APIs.13960MIT- AlicenseAqualityDmaintenanceA Model Context Protocol server providing tools for DB queries, API calls, file I/O, and text transformations, enabling AI agents like Claude to perform real-world actions.10MIT
TDQS
C2.6/5.0
Scored across 22 tools
Disambiguation2/5
Multiple tools (microcms_create_content_published, microcms_patch_content, microcms_update_content_draft) have identical descriptions that claim to create new content and publish immediately, making it impossible to distinguish their actual purpose. The overlap between create, patch, and update variants is severe.
Naming Consistency3/5
All tools use the microcms_ prefix and snake_case, following a verb_noun pattern. However, there are inconsistencies like microcms_create_contents_bulk vs microcms_create_content (plural vs singular), and the verbs 'patch' vs 'update' are used without clear distinction.
Tool Count3/5
22 tools is on the high side for a CMS MCP server, but the scope covers content, media, members, services, and APIs. Some consolidation could reduce redundancy, but the count is still reasonable.
Completeness3/5
The tool set covers most CRUD operations for content and media, plus metadata, member info, and service discovery. Missing are bulk update/delete and member management (create/update/delete). The duplicate create/patch tools obscure actual functionality.
Maintenance
ActivityActive
ResponsivenessSlow