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. |
| Node HTTP transport and release candidate | Markdown source of one documentation page. |
| docs-mcp | An MCP server that lets AI agents search and read your documentation at query time instead of relying on stale training data. |
| SDK v2 migration | Markdown source of one documentation page. |
| Tools | Reference for the search_docs, get_doc and list_docs tools and the docs:// resource. |
| WebMCP | Expose the docs tools to browser agents on your docs site through WebMCP, so they call tools instead of scraping pages. |
| Apideck Docs MCP | Markdown source of one documentation page. |
| Releasing | Markdown source of one documentation page. |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: search_docs performs full-text search, get_doc retrieves a specific page or section by path, and list_docs browses page metadata. The descriptions explicitly clarify when to use each and how they relate, leaving little room for misselection.
All three tools follow a consistent snake_case verb_noun convention: search_docs, get_doc, list_docs. The pattern is predictable and readable across the entire set.
Three tools are well-scoped for a documentation server: search, retrieve, and list form a compact and complete read-only surface. No tool feels redundant or missing at this scope.
For a read-only documentation server, the surface covers discovery (list_docs), search (search_docs), and retrieval of full pages or sections (get_doc). There are no obvious operational gaps for the stated purpose.