MCP Documentation Server

What is MCP Documentation Server?

The MCP Documentation Server is a customized version of the MCP documentation server that enables integration between LLM applications (like Cursor, Claude Desktop, Windsurf) and documentation sources via the Model Context Protocol. It provides access to specific documentation files (langgraph.txt and mcp.txt) and tools to fetch documentation from URLs within those files.

How to use MCP Documentation Server?

Clone the repository, create a virtual environment, install the package in development mode (pip install -e .), then run the server using the installed command mcpdoc with a JSON config file and transport options (SSE or stdio). For IDE integration like Cursor, add a configuration to ~/.cursor/mcp.json using UV and set custom instructions to guide the LLM to use the server's tools.

Key features of MCP Documentation Server

• Integration with MCP host applications like Cursor, Claude Desktop, Windsurf
• Access to LangGraph and MCP documentation files
• Tools to fetch documentation from URLs listed in those files
• Support for SSE and stdio transport protocols
• Configurable allowed domains for security
• Easy setup via pip or UV

Use cases of MCP Documentation Server

• Answering questions about LangGraph by fetching relevant documentation
• Answering questions about Model Context Protocol (MCP) using its docs
• Enabling LLM applications to automatically retrieve and reflect on documentation URLs
• Customizing allowed domains to restrict or permit documentation sources

FAQ from MCP Documentation Server

What documentation sources are available?

The server is currently set up for LangGraph Documentation and MCP Documentation, sourced from specific URLs.

How do I run the server?

You can run the server using the mcpdoc command with a config file, transport (SSE or stdio), port, and host. Alternatively, you can use UV with the uvx --from mcpdoc mcpdoc command.

How do I integrate with Cursor?

Add a configuration entry to ~/.cursor/mcp.json and provide custom instructions in Cursor to call list_doc_sources and fetch_docs tools.

What security controls are available?

Strict domain access controls: remote documentation files allow only the specific domain by default; local files allow none. Use --allowed-domains to explicitly add domains or * to allow all.

What is the relationship to the original mcpdoc?

This server is a modified version of the original mcpdoc by LangChain AI, customized to provide focused access to LangGraph and MCP documentation.