local-docs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOCS_ROOT | Yes | Path to the root directory containing documents to search and read. |
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_documentsA | 検索対象フォルダ (DOCS_ROOT) 配下のドキュメント一覧を返す。 |
| search_documentsA | DOCS_ROOT 配下のドキュメントを全文検索する。 |
| read_documentA | ドキュメントの本文をテキスト(Markdown)として読み出す。 |
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 has a clearly distinct purpose: listing all documents, reading a specific document with pagination, and full-text searching. No ambiguity or overlap.
All tool names follow a consistent verb_noun pattern in snake_case (list_documents, read_document, search_documents), making them predictable.
Three tools are well-scoped for a document server, covering the essential operations without unnecessary bloat or deficiency.
The tool set provides listing, reading with pagination, and full-text search, which is complete for a read-only document retrieval system. No obvious gaps.