read-docs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | Operating mode for the MCP server. Options: 'normal' (default), 'two-step'. | normal |
| name | No | Name of the package/library. Required for Read Documentation Mode. | |
| branch | No | Branch to read the docs from. | main |
| docs-path | No | Path to the docs folder. | docs |
| include-src | No | Include source code reading capability. Set to 'true' to enable reading source files. Default: 'false'. | false |
| git-repo-path | No | Path to the git repository (http or ssh). Required for Read Documentation Mode. | |
| clone-location | No | Path to clone the git repository. Default is {os home directory}/.temp-repo | |
| personal-token | No | Personal access token for git authentication. Optional, recommended for private repositories. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-create-docs-instructionsB | Get instructions to create a new document |
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
Only one tool exists, so there is no possibility of confusion or overlap. The tool's purpose is clear from its description.
With only one tool, naming consistency cannot be fully assessed, but the name follows a verb-object pattern ('get' + 'create-docs-instructions'). The compound object is slightly awkward but not inconsistent.
A single tool feels thin for a server named 'read-docs-mcp'. The tool count is at the borderline of being insufficient for any meaningful workflow.
The server name suggests a documentation reading purpose, but the only tool is about creating docs. There are no read, list, search, or update capabilities, making the surface severely incomplete for its apparent domain.