The Cargo Doc MCP Server provides tools to manage and query Rust documentation locally.
Get Crate Documentation: Retrieve the main documentation page of a crate to understand its concepts and usage.
List Symbols: Explore all symbols (structs, enums, traits, etc.) within a crate's documentation.
Search Documentation: Search within a crate's documentation for specific features, error messages, or usage examples.
Enables management of Rust documentation through cargo doc commands, providing tools to check, build, and search Rust documentation locally. Features include retrieving crate documentation pages, listing symbols (structs, enums, traits), and searching within crate documentation.
cargo doc MCP Server
A MCP server for managing Rust documentation through cargo doc commands. This server provides tools to check, build, and search Rust documentation locally.
Features
Tools
get_crate_doc- Get crate's main documentation page for understanding overall concepts and usageParameters:
project_path: Path to the Rust project (must be absolute path)crate_name: Name of the crate to get documentation for
list_symbols- List all symbols (structs, enums, traits, etc.) in a crate's documentationParameters:
project_path: Path to the Rust project (must be absolute path)crate_name: Name of the crate to list symbols for
search_doc- Search within a crate's documentationParameters:
project_path: Path to the Rust project (must be absolute path)crate_name: Name of the crate to search inquery: Search query (keyword or symbol)limit(optional): Maximum number of results to return (default: 10)
Related MCP server: McpDocServer
Requirements
Node.js 16 or later
Rust and Cargo installed
Installation
Install dependencies:
Build the server:
For development with auto-rebuild:
Usage
Add the following configuration:
Debugging
Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector:
The Inspector will provide a URL to access debugging tools in your browser.
Cache System
The server maintains a cache of built documentation paths to improve performance. Cache entries expire after 24 hours to ensure documentation stays up-to-date.
License
MIT