mcp-for-docs
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOCS_BASE_PATH | No | Where to store all documentation. Overrides the docsBasePath setting in config.json |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| crawl_documentationC | Crawl and download documentation from a website |
| generate_cheatsheetC | Generate a cheat sheet from documentation |
| list_documentationC | List available documentation |
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 3 tools
Each tool has a clearly distinct purpose: crawling/downloading documentation, generating a cheat sheet from it, and listing available documentation. There is no overlap in functionality, making it easy for an agent to select the right tool.
All tool names follow a consistent verb_noun pattern (crawl_documentation, generate_cheatsheet, list_documentation) with snake_case throughout. This predictability aids in tool discovery and usage.
With only 3 tools, the set feels thin for a documentation management server. While the tools cover core operations, more comprehensive coverage (e.g., search, update, or delete documentation) would be expected for such a domain.
The tools cover listing, crawling, and generating cheat sheets, but there are notable gaps. Missing operations like searching within documentation, updating or deleting documentation, or managing documentation metadata limit the server's utility for full lifecycle management.