read-docs-mcp

A Model Context Protocol (MCP) server that enables AI agents to access and understand package documentation through a structured interface.

Features

• Automatically generates MCP tools from documentation structure
• Supports multiple documentation modules (hooks, components, utilities, etc.)
• Configurable naming patterns for documentation files and module folders
• Provides listing, overview, and detailed documentation access
• Dynamic tool generation based on configured modules
• Fallback to package.json for version information
• Customizable documentation path
• Fuzzy search capability to find files by keyword with smart prioritization

Dual Usage Modes

This MCP server has two distinct usage modes:

1. Read Documentation Mode (read-docs-{name}): When both name and git-repo-path are provided, the server functions as a document reader for the specified repository, generating tools to access the documentation.

2. Create Documentation Mode (create-read-docs): When no repository information is provided, the server functions as a guide for creating documentation structure, providing instructions on how to set up documentation files.

Configuration

The MCP supports the following command-line arguments:

• --name: Name of the package/library (required for Read Documentation Mode)
• --git-repo-path: Path to the git repository (http or ssh) (required for Read Documentation Mode)
  • If not provided, the MCP server will only provide construction instructions
• --branch: Branch to read the docs from
  • Default: main
• --docs-path: Path to the docs folder
  • Default: docs
• --clone-location: Path to clone the git repository
  • Default: {os home directory}/.temp-repo
• --mode: Operating mode for the MCP server
  • Options: normal (default), two-step
  • See Operating Modes section for details

Important Note on Git Authentication

This MCP requires direct cloning of the target git repository. You must ensure you have proper access to the repository before using this tool. For private repositories, make sure:

1. Your local machine has the necessary SSH keys configured for SSH URLs
2. For HTTPS URLs, you've either:
   • Used a personal access token in the URL
   • Configured Git credential storage on your machine

Without proper authentication, the MCP will fail to clone private repositories.

Operating Modes

You can specify different modes when running the MCP server using the --mode argument:

Normal Mode (default)

npx -y read-docs-mcp --name=MyDocs --git-repo-path=https://github.com/user/repo
# or explicitly:
npx -y read-docs-mcp --name=MyDocs --git-repo-path=https://github.com/user/repo --mode=normal

In normal mode, the server creates individual tools for each module and operation (e.g., get-hooks-list, get-hooks-details, get-components-list, etc.).

Two-Step Mode

npx -y read-docs-mcp --name=MyDocs --git-repo-path=https://github.com/user/repo --mode=two-step

In two-step mode, instead of creating individual tools for each module, the server creates these 5 generic tools:

1. get-overview - Get overview of the project (same as normal mode)
2. get-overall-list - Get a list of all available modules
3. get-module-overview - Get overview of a specific module (takes module name as parameter)
4. get-module-list - Get list of items in a specific module (takes module name as parameter)
5. get-module-detail - Get details of a specific item in a module (takes module and item name as parameters)

This approach reduces the total number of tools significantly when you have many modules, making the MCP server more efficient and easier to manage.

Setting up in Cursor

To use this MCP in Cursor, add the following configuration to your Cursor settings:

Read Documentation Mode (Mac/Linux)

{
  "mcpServers": {
    "read-docs-{name}": {
      "command": "npx",
      "args": [
        "-y",
        "read-docs-mcp",
        "--git-repo-path=https://github.com/user/repo",
        "--name=YourLibName"
      ]
    }
  }
}

Create Documentation Mode (Mac/Linux)

{
  "mcpServers": {
    "create-read-docs": {
      "command": "npx",
      "args": ["-y", "read-docs-mcp"]
    }
  }
}

Read Documentation Mode (Windows)

{
  "mcpServers": {
    "read-docs-{name}": {
      "command": "cmd",
      "args": [
        "/c",
        "npx",
        "-y",
        "read-docs-mcp",
        "--git-repo-path=https://github.com/user/repo",
        "--name=YourLibName"
      ]
    }
  }
}

Create Documentation Mode (Windows)

{
  "mcpServers": {
    "create-read-docs": {
      "command": "cmd",
      "args": ["/c", "npx", "-y", "read-docs-mcp"]
    }
  }
}

Custom Documentation Path

If you want to specify a custom documentation directory:

{
  "mcpServers": {
    "read-docs-{name}": {
      "command": "npx",
      "args": [
        "-y",
        "read-docs-mcp",
        "--git-repo-path=https://github.com/user/repo",
        "--name=YourLibName",
        "--docs-path=documentation"
      ]
    }
  }
}

Two-Step Mode Configuration

To use two-step mode for better efficiency with large documentation sets:

{
  "mcpServers": {
    "read-docs-{name}": {
      "command": "npx",
      "args": [
        "-y",
        "read-docs-mcp",
        "--git-repo-path=https://github.com/user/repo",
        "--name=YourLibName",
        "--mode=two-step"
      ]
    }
  }
}

Documentation Structure

The MCP server expects the following structure for Read Documentation Mode:

repository/
├── docs/ (configurable)
│   ├── read-docs-mcp.json
│   ├── hooks/
│   │   ├── read-module-docs-mcp.json
│   │   ├── list.md
│   │   ├── overview.md
│   │   ├── use-state.md
│   │   └── ...
│   ├── components/
│   │   ├── read-module-docs-mcp.json
│   │   └── ...
│   └── ...
└── package.json

Main Configuration: read-docs-mcp.json

{
  "name": "SomeLibrary",
  "description": "A library for some purpose",
  "version": "1.0.1",
  "moduleList": ["hooks", "components", "directives", "utils"],
  "fileName": "overview.md",
  "moduleFolderNamingPattern": "kebab"
}

• name, description: Used in MCP server construction
• version: If not provided, falls back to version in package.json, or defaults to "0.1.0"
• moduleList: List of documentation modules; if not provided, all folders in the docs directory are used
• fileName: The file to use for the overview. If not provided, defaults to "overview.md"
• moduleFolderNamingPattern: Naming pattern for module folders. Can be "kebab", "camel", "snake", "pascal", or "original". Default is "kebab"

Naming Pattern Rules

The following naming patterns are supported for module folders and detail files:

• kebab-case (default): Words are lowercase and separated by hyphens

  • Example: "form-control", "use-state", "data-table"

• camelCase: First word is lowercase, subsequent words are capitalized with no separators

  • Example: "formControl", "useState", "dataTable"

• snake_case: Words are lowercase and separated by underscores

  • Example: "form_control", "use_state", "data_table"

• PascalCase: Each word is capitalized with no separators

  • Example: "FormControl", "UseState", "DataTable"

• original: Uses the name exactly as provided in the moduleList, with no conversion

  • Example: Names in moduleList will be used as-is for directory names

Module Configuration: read-module-docs-mcp.json

{
  "get-all": {
    "name": "get-hook-list",
    "description": "Get a list of hooks",
    "fileName": "list.md"
  },
  "get-details": {
    "name": "get-hook-details",
    "description": "Get details of a hook",
    "paramDescription": "A hook name",
    "namingPattern": "kebab"
  },
  "get-overview": {
    "name": "get-hook-overview",
    "description": "Get an overview of the hook module",
    "fileName": "overview.md"
  }
}

Working with Agents

Using Read Documentation Mode

When you have set up the MCP server with a repository, you can use it to explore documentation:

Using the read-docs-{YourLibName} MCP, I'd like to explore the documentation for {YourLibName}. Can you:

1. Get an overview of the available modules
2. Show me the list of hooks available
3. Provide details on a specific hook
4. Give me an overview of the components module

Using Create Documentation Mode

When you use the MCP server without a repository, you can ask for help creating documentation:

Using the create-read-docs MCP, I need to create documentation for my library that can be used with read-docs-mcp.
Can you help me set up the required structure and files?

Example Prompts for Read Documentation Mode

Exploring Package Documentation

Using the read-docs-{PackageName} MCP, I'd like to explore the documentation for [Package Name]. Can you:

1. Get an overview of the available modules
2. Show me the list of hooks available
3. Provide details on the useAuth hook
4. Give me an overview of the components module

I'm particularly interested in understanding how authentication works in this library.

Learning How to Use a Component

Using the read-docs-{PackageName} MCP, I need to implement a form with validation using the [Package Name] library. Please:

1. Show me the available components
2. Get details on the Form component
3. Get details on the Input component
4. Explain how to use form validation with these components

If there are any code examples in the documentation, please highlight those.

Finding Documentation with Fuzzy Search

Using the read-docs-{PackageName} MCP, I'm looking for documentation about authentication in the library. Can you:

1. Use fuzzy search to find all files related to "auth"
2. Based on the search results, get the details for the most relevant authentication documentation
3. Show me how to implement authentication using the library

The fuzzy search should help us quickly locate the relevant documentation files.

Example Prompts for Create Documentation Mode

Using the create-read-docs MCP, I need to set up documentation for my React component library. Can you help me create the folder structure and necessary configuration files?

Using the create-read-docs MCP, I've started creating documentation for my utility functions. How should I structure the detailed documentation for individual utility functions?

Tools

Read Documentation Mode Tools

The MCP dynamically generates tools based on the documentation structure and operating mode. All tools are prefixed with the package name to avoid conflicts when multiple read-docs-mcp instances are used.

Normal Mode Tools

In normal mode, for each module in the moduleList, up to three tools can be generated:

{name}-get-[module]-list

Get a list of all items in the module.

Parameters:

• None

Returns:

• Content of the list file (default: list.md)

{name}-get-[module]-details

Get details about a specific item in the module.

Parameters:

• name (string): Name of the item to get details for

Returns:

• Content of the details file, named according to the namingPattern (default is kebab-case)

{name}-get-[module]-overview

Get an overview of the module.

Parameters:

• None

Returns:

• Content of the overview file (default: overview.md)

{name}-fuzzy-search

Search for files by keyword with intelligent prioritization.

Parameters:

• keyword (string): The keyword to search for in file names and content

Returns:

• Formatted list of matching files with the following priority:
  1. Exact match in file name
  2. Partial match in file name
  3. Exact match in file content
  4. Partial match in file content

Results are formatted as:

type: module
name: someModule

or

type: detail
name: someDetail
module: someModule

Two-Step Mode Tools

In two-step mode, the MCP generates 5 generic tools instead of individual tools for each module:

{name}-get-overview

Get overview of the project.

Parameters:

• None

Returns:

• Content of the main overview file

{name}-get-overall-list

Get a list of all available modules.

Parameters:

• None

Returns:

• List of all modules available in the documentation

{name}-get-module-overview

Get an overview of a specific module.

Parameters:

• module (string): Name of the module

Returns:

• Content of the module's overview file

{name}-get-module-list

Get a list of items in a specific module.

Parameters:

• module (string): Name of the module

Returns:

• Content of the module's list file

{name}-get-module-detail

Get details of a specific item in a module.

Parameters:

• module (string): Name of the module
• name (string): Name of the item to get details for

Returns:

• Content of the item's details file

{name}-fuzzy-search

Search for files by keyword with intelligent prioritization.

Parameters:

• keyword (string): The keyword to search for in file names and content

Returns:

• Formatted list of matching files with the same priority system and format as described in the Normal Mode section above

Create Documentation Mode Tools

The MCP provides a single tool to help with creating documentation:

get-create-docs-instructions

Get detailed instructions for creating documentation structure.

Parameters:

• None

Returns:

• Detailed instructions on setting up documentation files and structure

Creating Documentation for Read Documentation Mode

You can either manually create the documentation structure or use the Create Documentation Mode to get guidance. Follow these steps to create documentation that can be accessed by the Read Documentation Mode:

Step 1: Create the main configuration file

Create a read-docs-mcp.json file in your documentation directory:

{
  "name": "YourLibrary",
  "description": "Description of your library",
  "version": "1.0.0",
  "moduleList": ["hooks", "components", "utils"],
  "moduleFolderNamingPattern": "kebab"
}

The moduleFolderNamingPattern determines how your module folder names will be converted. For example, if your moduleList contains ["FormControl", "useHooks"] and you choose "kebab" pattern, the folders will be created as form-control/ and use-hooks/.

Step 2: Create module directories and configurations

For each module, create a directory and a read-module-docs-mcp.json file:

{
  "get-all": {
    "name": "get-component-list",
    "description": "Get a list of components",
    "fileName": "list.md"
  },
  "get-details": {
    "name": "get-component-details",
    "description": "Get details of a component",
    "paramDescription": "A component name",
    "namingPattern": "kebab"
  },
  "get-overview": {
    "name": "get-component-overview",
    "description": "Get an overview of components",
    "fileName": "overview.md"
  }
}

Note: The actual tool names generated will be prefixed with your package name. For example, if your package name is "MyLibrary", the tools will be named MyLibrary-get-component-list, MyLibrary-get-component-details, etc.

Step 3: Create documentation files

Create the necessary markdown files:

• list.md - List of all items in the module
• overview.md - Overview of the module
• Individual detail files (e.g., button.md, input.md, etc.)

License

MIT