Docs Provider MCP server

This MCP Docs Provider acts as a documentation context provider for LLMs via the Model Context Protocol (MCP). It allows AI models to seamlessly access and query your local markdown technical documentation, making it easier to reference documentation during conversations.

Installation Options

Installing via Smithery

You can automatically install mcp-docs-provider for Claude Desktop using Smithery:

npx -y @smithery/cli install @YassineTk/mcp-docs-provider --client claude

Configuration

Setting Up with Cursor

To configure the MCP Docs Provider with Cursor, add the following to your Cursor configuration file (mcp.json):

{
  "mcpServers": {
    "mcp-docs-provider": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-docs-provider",
        "/path/to/your/documentation.md"
      ]
    }
  }
}

Make sure to replace /path/to/your/documentation.md with the actual path to your markdown documentation file. No rebuild is required after updating your Markdown documentation.

Configuring MCP Client Rules

For automatic usage of your documentation without explicitly mentioning "Using my MCP" in queries, add this specification to your MCP Client Rules in Cursor:

"If a user ask you about ui pattern then follow the mcp-docs-provider MCP server."

Usage

Once configured, your AI assistant will automatically reference the provided documentation when responding to relevant queries. You don't need to explicitly tell the AI to use the documentation - it will happen automatically based on the client rules you've set up.

The MCP Docs Provider allows your AI assistant to:

• Search through your documentation
• Reference specific sections
• Provide more accurate and contextual responses based on your documentation

How to install this MCP server

For Claude Code

To add this MCP server to Claude Code, run this command in your terminal:

claude mcp add-json "mcp-docs-provider" '{"command":"npx","args":["-y","mcp-docs-provider","/path/to/your/documentation.md"]}'

See the official Claude Code MCP documentation for more details.

For Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

{
    "mcpServers": {
        "mcp-docs-provider": {
            "command": "npx",
            "args": [
                "-y",
                "mcp-docs-provider",
                "/path/to/your/documentation.md"
            ]
        }
    }
}

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.

For Claude Desktop

To add this MCP server to Claude Desktop:

1. Find your configuration file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json
• Linux: ~/.config/Claude/claude_desktop_config.json

2. Add this to your configuration file:

{
    "mcpServers": {
        "mcp-docs-provider": {
            "command": "npx",
            "args": [
                "-y",
                "mcp-docs-provider",
                "/path/to/your/documentation.md"
            ]
        }
    }
}

3. Restart Claude Desktop for the changes to take effect