Docs MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GIT_REF | No | The branch, tag, or commit hash to use from the Git repository. | main |
| GIT_URL | No | URL of the Git repository to clone for documentation content. | |
| DATA_DIR | No | Path to the directory containing the content to be searched at runtime. Overrides content sourced from includeDir or gitUrl defined in the config file or built into the package. | |
| TOOL_NAME | No | The name of the MCP tool exposed by the server. | search_docs |
| TOOL_DESCRIPTION | No | The description of the MCP tool shown to AI assistants. | Search documentation using the probe search engine. |
| AUTO_UPDATE_INTERVAL | No | Interval in minutes to automatically check for Git updates (0 means disabled). Setting this to a value > 0 enables Git cloning and periodic git pull operations. | 0 |
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 |
|---|---|
| search_docsA | Search documentation using the probe search engine. |
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 1 tool
With only one tool, there is no risk of confusion or overlap between tools.
Single tool, so naming consistency is perfect by default.
A single tool for a documentation search server is too few, limiting its utility.
Only search is provided; missing tools to list, retrieve, or manage documentation sources.