docs-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOCS_DIR | Yes | Path to the folder of Markdown documentation (equivalent to the --docs flag) | |
| DOCS_NAME | No | Name of the MCP server (equivalent to the --name flag) | |
| DOCS_ABOUT | No | Description of the documentation (equivalent to the --about flag) | |
| DOCS_BASE_URL | No | Base URL for the documentation site (equivalent to the --base-url flag) |
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 |
|---|---|
| search_docsA | Full-text search over the documentation. Returns matching sections with a snippet, the page path and heading anchor. Call get_doc with a returned path to read the full page or a single section. |
| get_docA | Return the full markdown of a documentation page by path, or a single section of it. Use search_docs or list_docs to find paths. |
| list_docsA | List documentation pages with their path, title, description and last-modified date. Useful to browse the structure before searching or to find pages under a prefix. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Auditing your docs | Check that documentation is complete, current and structured to return useful results before exposing it to agents. |
| Getting started | Install docs-mcp, point it at a docs folder, and connect it to Claude Code or another MCP client. |
| Hosting | Run docs-mcp as a public Streamable HTTP endpoint on Vercel or any Node host. |
| docs-mcp | An MCP server that lets AI agents search and read your documentation at query time instead of relying on stale training data. |
| Tools | Reference for the search_docs, get_doc and list_docs tools and the docs:// resource. |
| docs-mcp | Markdown source of one documentation page. |
TDQS
Scored across 3 tools
Each tool targets a clearly distinct operation: list_docs for browsing structure, search_docs for full-text queries, and get_doc for retrieving content by path. The descriptions explicitly cross-reference each other, reinforcing the intended workflow.
All three tools follow the same noun-prefixed pattern with a consistent verb (get_doc, list_docs, search_docs), using uniform snake_case throughout. No deviations or mixing of conventions.
Three tools cover the core read-only documentation workflow (browse, search, fetch) without redundancy. Slightly lean, but each tool earns its place and the scope is well-defined.
The browse/search/retrieve lifecycle is fully covered for consuming docs, with get_doc supporting both whole-page and section retrieval. Writing or indexing operations are absent, but may be intentionally out of scope for a read-oriented server.