Docs-MCP
Server 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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_docsA | 所持しているドキュメントの一覧を取得 |
| get_docA | 指定したドキュメントの内容を取得（ページネーション対応） |
| grep_docsA | ドキュメント内をgrepで検索 |
| semantic_searchB | 意味的に関連する内容を検索 |
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
Each tool serves a distinct purpose: listing documents, retrieving content, regex search, and semantic search. No overlap exists.
All tool names follow a consistent verb_noun pattern (get_doc, grep_docs, list_docs, semantic_search).
With 4 tools, the set is well-scoped for a documentation server, covering essential operations without bloat.
The tool surface covers the full lifecycle of reading documentation: listing, retrieving, and two complementary search methods.