DocGen MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| create_documentationC | Create documentation from source files using a template |
| list_templatesC | List available documentation templates |
| view_document_historyB | View history of previously generated documents |
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: create_documentation generates new docs, list_templates shows available templates, and view_document_history accesses past outputs. There is no overlap or ambiguity between these functions.
All tools follow a consistent verb_noun pattern (create_documentation, list_templates, view_document_history) with snake_case throughout. The naming is predictable and readable.
With only 3 tools, the set feels thin for a documentation generation server. While it covers core operations, more tools might be expected for tasks like updating templates, deleting documents, or customizing generation parameters.
The tools cover creation, template listing, and history viewing, but there are notable gaps: no update or delete operations for documents or templates, and no way to customize generation beyond templates. This could limit agent workflows.