microCMS MCP Server
Related Servers
Alternatives to microCMS MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that bridges MCP clients with local LLM services, enabling seamless integration with MCP-compatible applications through standard tools like chat completion, model listing, and health checks.-
- AlicenseAqualityAmaintenanceA Model Context Protocol (MCP) server that helps large language models index, search, and analyze code repositories with minimal setup14696 PyPI1,002MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server designed to easily dump your codebase context into Large Language Models (LLMs).18 npm3Apache 2.0
- AlicenseBqualityDmaintenanceAn educational implementation of a Model Context Protocol server that demonstrates how to build a functional MCP server integrating with various LLM clients.2MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server built into a Next.js app that serves prompts via the Model Context Protocol, supporting local and cloud LLM providers.56 npm1MIT
- FlicenseDqualityDmaintenanceA ready-to-use starter implementation of the Model Context Protocol (MCP) server that enables applications to provide standardized context for LLMs with sample resources, tools, and prompts.212 npm1-
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: GetMicroCMSContent retrieves a specific item by ID, while SearchMicroCMS performs a broader query across content. There is no overlap in functionality, making it easy for an agent to choose the right tool for the task.
Both tools follow a consistent naming pattern with a verb (Get or Search) followed by the domain (MicroCMS) and a noun (Content). They use consistent PascalCase styling, making the naming predictable and readable.
With only two tools, the server feels under-scoped for a content management system. It lacks essential CRUD operations like create, update, or delete, which are typically expected for managing content. The count is too low for the apparent domain.
The toolset is severely incomplete for a CMS server. It only provides read operations (get and search), missing create, update, delete, and other lifecycle management functions. This will cause agent failures when full content management is required.