docstar-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | Yes | Your OpenAI API key |
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 |
|---|---|
| get_recent_changesC | Get recent git changes |
| generate_docs_for_changesC | Generate documentation for changes |
| apply_doc_updateC | Apply generated documentation to a file |
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
The three tools form a clear sequential pipeline: retrieve changes, generate docs, apply update. Each has a distinct action and resource, so an agent can easily select the right one.
All names use snake_case with a verb-first pattern (get_, generate_, apply_) followed by a noun/object. Consistent and predictable throughout.
Three tools perfectly match the narrow purpose of a documentation-generation pipeline; each earns its place with no redundancy.
The surface covers the end-to-end workflow (fetch, generate, apply) but lacks optional steps like previewing generated docs, targeting specific files, or rolling back changes.