docs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOCS_MCP_DEBUG | No | Set to '1' to print token usage to stderr. | 0 |
| 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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| createA | Write a software document (plan, RFC, design doc, README, guide, ADR) from facts you supply. Investigate the repository first, then pass what you learned as structured material. Do not draft prose yourself and do not paste a draft as material; a separate writing model decides structure and wording. When it returns, fact-check the document against the repository and send corrections through the edit tool as facts. |
| editA | Revise an existing document with the smallest coherent change. State what is factually wrong or what must change, as facts rather than replacement prose. The document's voice and untouched text are preserved. |
| reviewA | Get editorial findings on a document: where it inventories instead of explains, structure that is not helping, missing motivation or tradeoffs, prose that reads like serialized code. Returns findings with locations, never a rewrite; "no significant editorial problems" is a possible outcome. |
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 distinct role: create produces a new document, edit modifies an existing one, and review provides editorial feedback. There is no overlap in purpose or action.
All tool names are single, lowercase verbs (create, edit, review), following a simple and predictable pattern. The naming style is uniform across the set.
Three tools form a tight, focused set for document lifecycle management. The scope is small but complete, and each tool serves a necessary function.
The set covers the core document workflow: creation, revision, and critique. There are no obvious dead ends, and the tools complement each other to support a complete editing cycle.