microCMS Document MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_generalA | microCMSについての質問に答える場合、まずこのツールを利用します。docs/general.md の内容を返します。これにはmicroCMS全体の概要や共通情報が書かれています。 |
| list_documentsA | microCMSについての質問に答える場合に利用します。ドキュメントディレクトリのファイル名一覧を返します。カテゴリーを指定することで特定のサブディレクトリのみを対象にできます。 まだ |
| search_documentA | microCMSについての質問に答える場合に利用します。ドキュメントから指定されたファイルを検索し、中身を返します。カテゴリーを指定することで特定のサブディレクトリのみを対象にできます。 まだ |
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 3 tools
Each tool serves a distinct purpose: fetch_general provides an overview, list_documents enumerates available files, and search_document retrieves specific file content. No overlap.
All tools use the verb_noun naming pattern with underscores (fetch_general, list_documents, search_document), providing clear and predictable naming.
Three tools are appropriate for a documentation server: one for overview, one for listing, one for retrieval. The count is well-scoped for the stated purpose.
The toolset covers basic read operations but lacks full-text search across all documents. However, the workflow (general → list → search) enables comprehensive Q&A, so only a minor gap exists.