docs2prompt MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | GitHub access token for accessing 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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_docs2prompt_docsA | |
| get_url_docsB | |
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 2 tools
The two tools have clearly distinct purposes: one retrieves documentation from a GitHub repository, the other from a generic URL. There is no ambiguity between them.
Both tools follow a consistent 'get_<source>_docs' pattern, making their purpose immediately clear and predictable.
With only two tools, the server is minimal but focused. The count is slightly low for broad usefulness, but it may be appropriate for a narrowly scoped documentation retrieval service.
The tools cover retrieval from two common sources, but the server name 'docs2prompt' suggests conversion to prompts, which is missing. The current surface is incomplete for the implied purpose.