Docs 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
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 |
|---|---|
| list_templatesA | List all available documentation templates from The Good Docs Project with IDs, names, and summaries. |
| search_templatesB | Search for the best documentation template based on keywords, document type, or task description (e.g. 'rest api', 'quick onboarding', 'bug tracking', 'installation', 'changelog', 'how to run docker'). |
| get_templateB | Get the raw Markdown template, official authoring guide, writing process instructions, and examples for a specific template ID. |
| get_style_guideA | Get The Good Docs Project comprehensive style guide and writing tips (voice, tone, terminology, formatting, minimalism, and readability standards). |
| generate_document_skeletonB | Generate a tailored document skeleton based on a The Good Docs Project template, substituting project metadata (title, overview, prerequisites, author, etc.) into the structured template. |
| save_documentA | Write the generated documentation directly to a file on the local filesystem (e.g. README.md, docs/quickstart.md, CONTRIBUTING.md). |
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 6 tools
The tools cover distinct stages of a documentation workflow: listing templates, searching templates, retrieving a specific template, getting a style guide, generating a tailored skeleton, and saving the result. list_templates vs search_templates vs get_template are clearly differentiated by scope and input.
All tool names use consistent snake_case with a leading verb, e.g. list_templates, search_templates, get_template, generate_document_skeleton, save_document. The pattern is predictable and readable throughout.
Six tools is a well-scoped set for a documentation template assistant. Each tool maps to a meaningful step and none appear redundant or unnecessary.
The core workflow is covered: discover templates, search, retrieve content, apply style guidance, generate a skeleton, and save it to disk. Minor gaps exist around editing or updating existing documents, validating generated output, or managing multiple saved documents, but these are not critical for the stated purpose.