MCP Docs Provider

You can run an MCP server that exposes your local markdown documentation to AI models, enabling fast, context-aware queries and helping models stay aligned with your own docs. This server acts as a dedicated provider that your MCP client can query to retrieve relevant documentation content on demand.

How to use

Use an MCP client to connect to the mcp-docs-provider server so your AI models can access your local markdown docs. The server is designed to automatically provide documentation context when you ask questions related to your UI patterns or other topics covered in your docs. You configure the client to route relevant queries through this provider without needing to reference the docs explicitly in every query.

Typical usage involves starting the MCP server on your machine and pointing your MCP client to it. When you ask about supported UI patterns or other documentation topics, the client will fetch the most relevant sections from your markdown file through the provider and include that context in the model’s response.

How to install

Prerequisites: you need Node.js and npm installed on your system. Verify installation with node -v and npm -v.

Install the MCP Docs Provider for your MCP client using the following command. This set includes automating the provider install for a Claude client via Smithery.

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

Configuration with cursor

Add the MCP server configuration to your Cursor setup to point the client at the docs provider. Use the following example and replace the path with the location of your documentation file.

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

Notes on updates and rules

No rebuild is required after updating your Markdown documentation. The provider serves updated content directly from the document as long as the path is correctly configured.

For client behavior, you can add a rule so that queries related to UI patterns automatically leverage the mcp-docs-provider context. Example rule: "If a user ask you about ui pattern then follow the mcp-docs-provider MCP server."