Skip to main content
Glama
Docs MCP Server
by yashisrani

Docs MCP Server

A Model Context Protocol server for generating professional, structured documentation using The Good Docs Project templates and authoring guidelines.

Description

The Docs Model Context Protocol server offers tools to improve the developer experience when creating technical documentation with agentic AI tools. Developers no longer need to worry about documentation formatting, missing sections, or inconsistent style. Simply prompt your agent, and the Docs MCP server locates the appropriate template, retrieves official authoring guidelines, and scaffolds or writes the document directly to your project.

Related MCP server: mcp-docs-tools

Key Features

  • Scaffolds 25+ industry-standard documentation types developed by The Good Docs Project (API reference, quickstarts, concepts, how-to guides, changelogs, architecture guides, and more)

  • Provides access to official authoring guides, writing processes, and real-world reference examples

  • Delivers the comprehensive Good Docs Project Style Guide and writing tips (voice, tone, terminology, and readability standards)

  • Integrates directly with agentic AI tools (Claude Desktop, VS Code, Cursor, Cline, Claude Code, Antigravity) with zero local setup required via npx

  • Enables safe writing of generated markdown documentation directly to project files

TIP

The template bundle is pre-compiled into the package, keeping the download size under 180 KB with fast startup times.

How It Works (Intelligent Template Selection)

You do not need to memorize or specify any template names. When you give a prompt such as "Create documentation for this feature" or "Document our Redis caching system":

  1. Codebase Understanding: The AI agent inspects your code to understand what the feature, API, or system does.

  2. Semantic Template Matching: The agent invokes the search_templates tool. The server applies semantic intent scoring across template names, tags, and summaries (for example, mapping "feature" to architecture/concepts, "endpoints" to API references, or "install/setup" to quickstarts and installation guides).

  3. Guideline & Template Retrieval: The agent fetches the matched template and its official Good Docs Project authoring guide.

  4. Drafting & Saving: The agent populates the template with real details from your codebase and writes the completed markdown document directly into your project.

If you do want a specific document type (e.g. "Create a quickstart guide" or "Write an API reference"), the agent will honor your specific choice.

Available Tools

  • list_templates: Lists all available documentation templates from The Good Docs Project with IDs, names, and summaries.

  • search_templates: Searches for the best documentation template based on keywords, document type, or task description.

  • get_template: Retrieves the raw Markdown template, official authoring guide, writing process instructions, and examples for a specific template ID.

  • get_style_guide: Provides access to The Good Docs Project style guide and technical writing guidelines (voice, tone, terminology, formatting, and readability).

  • generate_document_skeleton: Generates a tailored document skeleton based on a template, substituting project metadata into the structured template.

  • save_document: Writes the generated documentation directly to a file on the local filesystem.

Requirements

  • Node.js Version v18.0.0, v20.0.0, v22.0.0 or higher

  • npm Version v8.0.0 or higher

  • An MCP client, such as VS Code (GitHub Copilot), Claude Desktop, Cursor, Cline, Claude Code, or Antigravity

Setup & Installation

Option 1: Run directly from GitHub via npx (Zero local install)

Users can run the server directly from GitHub without cloning:

{
  "mcpServers": {
    "docs-mcp-server": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "github:yashisrani/Docs-MCP"
      ]
    }
  }
}

Option 2: Clone and Run Locally

  1. Clone the repository:

    git clone https://github.com/yashisrani/Docs-MCP.git
    cd Docs-MCP
    npm install
    npm run build
  2. Configure your MCP client:

    {
      "mcpServers": {
       "docs-mcp-server": {
         "type": "stdio",
         "command": "node",
         "args": [
           "/path/to/Docs-MCP/dist/index.js"
         ]
       }
     }
    }

Specific MCP Clients (via GitHub npx)

VS Code (GitHub Copilot / Chat)

code --add-mcp '{"name":"docs-mcp-server","type":"stdio","command":"npx","args":["-y","github:yashisrani/Docs-MCP"]}'

Claude Desktop

Add to claude_desktop_config.json:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "docs-mcp-server": {
      "command": "npx",
      "args": ["-y", "github:yashisrani/Docs-MCP"]
    }
  }
}

Cline

  1. Open the Cline panel in VS Code.

  2. Click on the "MCP Servers" icon at the top, next to the plus symbol.

  3. Switch to the "Configure" tab, then click "Configure MCP servers".

  4. Insert the configuration:

{
  "mcpServers": {
    "docs-mcp-server": {
      "command": "npx",
      "args": ["-y", "github:yashisrani/Docs-MCP"]
    }
  }
}

Claude Code

claude mcp add --transport stdio --scope user docs-mcp-server -- npx -y github:yashisrani/Docs-MCP

Codex

codex mcp add --transport stdio docs-mcp-server -- npx -y github:yashisrani/Docs-MCP

Cursor / Windsurf / Antigravity

In your MCP settings panel or config file, add:

  • Name: docs-mcp-server

  • Transport: stdio

  • Command: npx

  • Args: ["-y", "github:yashisrani/Docs-MCP"]


Adding Rules to your Project

The following rules guide large language models (LLMs) in using the Docs MCP server correctly. Add these rules to your global or project-specific AGENTS.md (or CLAUDE.md for Claude Code):

## Guidelines for Documentation

- When creating or updating documentation, use the `search_templates` or `list_templates` tools from the Docs MCP server to select the matching template from The Good Docs Project.
- Consult `get_style_guide` and `get_template` with `include_guide: true` to align with professional documentation standards (voice, tone, structure, and readability).
- Use `generate_document_skeleton` or `save_document` to produce complete, structured markdown files.

Example Prompts for Agents

Once connected, you can prompt your agent:

  1. Quickstart Guide:

    "Using docs-mcp, find the right template and write a quickstart guide for running our Postgres database with Docker Compose."

  2. API Reference:

    "Search docs-mcp for API reference templates, inspect the authoring guide, and generate an API reference for our user authentication service."

  3. Feature Overview / Concept Document:

    "Using docs-mcp, find the appropriate template for a new feature overview (e.g. Concept template) and write an architecture and feature guide for our Real-Time Collaboration feature."

  4. Contributing Guide:

    "Generate a CONTRIBUTING.md file for our open-source TypeScript library following The Good Docs Project standards."

  5. Troubleshooting Guide:

    "We have several common connection timeout errors. Pull the troubleshooting guide template from docs-mcp and draft a troubleshooting document."


Support, Feedback, Contributing

This project is open to feature requests, suggestions, and bug reports. Contributions and feedback are welcome.

For guidelines on writing and template structure, refer to The Good Docs Project.


Code of Conduct

Members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone. By participating in this project, you agree to abide by standard community conduct guidelines at all times.


Author & Creator

Created and maintained by Yash Israni.


Licensing

The MCP server codebase is created by Yash Israni and licensed under the MIT License.

Documentation templates and authoring guides are developed by and credited to The Good Docs Project.

Available Tools

6 tools
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.

Inputs: template_id (required), project_name (required), custom_sections, project_description.

get_style_guideA

Get The Good Docs Project comprehensive style guide and writing tips (voice, tone, terminology, formatting, minimalism, and readability standards).

Inputs: topic.

get_templateB

Get the raw Markdown template, official authoring guide, writing process instructions, and examples for a specific template ID.

Inputs: template_id (required), include_guide, include_example.

list_templatesA

List all available documentation templates from The Good Docs Project with IDs, names, and summaries.

Inputs: category.

save_documentA

Write the generated documentation directly to a file on the local filesystem (e.g. README.md, docs/quickstart.md, CONTRIBUTING.md).

Inputs: content (required), file_path (required), overwrite.

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').

Inputs: query (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to generate professional documentation using structured templates based on the POWER framework. Provides access to standardized templates for README, architecture, API, components, and schema documentation.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides documentation generation and analysis tools for AI agents, including JSDoc generation, README analysis, changelog generation, API documentation, and code comment analysis.
      39 npm
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to discover and invoke tools for saving and retrieving code snippets, generating style guides and wiki documentation, and orchestrating multi-agent documentation workflows with semantic search.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI models to search and retrieve up-to-date technical documentation for popular agent frameworks such as LangChain, LlamaIndex, AutoGen, Agno, OpenAI Agents SDK, MCP, Camel AI, and CrewAI via stdio or SSE transports.
      -