A
licenseA
qualityC
maintenanceA Model Context Protocol (MCP) server that helps large language models index, search, and analyze code repositories with minimal setup
22
14
2,766 PyPI
1,005
MIT
microCMS MCP Server
by SpringMT
Allows interaction with microCMS API to search and retrieve content from microCMS headless CMS instances.
Click on "Deploy 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., "@microCMS MCP Server search for blog posts about AI published this month"
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.
microCMS MCP Server
A Model Context Protocol (MCP) compatible microCMS search server that can be used to search and retrieve microCMS content from LLM.
function
Searching for content using the microCMS API
Getting specific content
MCP (Model Context Protocol) compliant interface
Related MCP server: @lex-tools/codebase-context-dumper
Description of required environment variables
MICROCMS_API_KEY: microCMS API key (required)MICROCMS_SERVICE_DOMAIN: microCMS service domain (required)MICROCMS_ENDPOINT: The endpoint to use.
Build
npm run buildHow to use
Usage from MCP client
This server complies with the MCP protocol and can therefore be called by any MCP-enabled LLM client.
{
"mcpServers": {
"microcms": {
"command": "node",
"args": [
"/ABSOLUTE/PATH/TO/PARENT/FOLDER/build/index.js"
],
"env": {
"MICROCMS_API_KEY": "",
"MICROCMS_SERVICE_DOMAIN": "",
"MICROCMS_ENDPOINT": ""
}
}
}
}Related links
Available Tools
2 toolsGetMicroCMSContentC
Get specific content from MicroCMS by ID
Inputs: endpoint (required), contentId (required), fields, depth.
SearchMicroCMSC
Search content in MicroCMS
Inputs: q (required), limit, offset, fields, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
B3/5.0
Scored across 2 tools
Disambiguation5/5
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.
Naming Consistency5/5
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.
Tool Count2/5
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.
Completeness2/5
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.
Maintenance
ActivityInactive
ResponsivenessNo recent community issues
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
MCP server for searching Airweave collections with natural language queries.
A Model Context Protocol server for Wix AI tools
Related MCP Servers
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server designed to easily dump your codebase context into Large Language Models (LLMs).12 npm3Apache 2.0
- AlicenseDqualityDmaintenanceA 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.25 npm1MIT
- AlicenseBqualityDmaintenanceAn educational implementation of a Model Context Protocol server that demonstrates how to build a functional MCP server integrating with various LLM clients.2MIT
