microCMS MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MICROCMS_API_KEY | Yes | Your microCMS API key | |
| MICROCMS_BASE_URL | Yes | Your microCMS base URL (e.g., https://your-service.microcms.io) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_contentsD | – |
| get_contentD | – |
| search_contentsD | – |
| filter_contentsD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Tool names suggest different operations (filter, get single, get all, search), but without descriptions, potential overlap between 'search_contents' and 'filter_contents' or 'get_contents' introduces ambiguity.
All tools follow a consistent verb_noun pattern (filter_contents, get_content, get_contents, search_contents) with no mixing of conventions.
Only 4 tools for a CMS server is far too few; typical CMS operations (create, update, delete, content type management) are missing, making the scope too narrow.
The tool set covers only read operations (get, filter, search), lacking essential CRUD operations (create, update, delete) and content lifecycle management.