Cargo Doc MCP Server

Provides an MCP server to manage, build, check, and search Rust documentation locally.

Local serverstdio 10

What is the Cargo Doc MCP server?

Cargo Doc MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Provides an MCP server to manage, build, check, and search Rust documentation locally.

What the assistant can call

Once Cargo Doc is connected, these are the calls the assistant has available:

  • get_crate_doc — Get crate's main documentation page for understanding overall concepts and usage
  • Parameters — - 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 documentation
  • search_doc — Search within a crate's documentation
  • query — Search query (keyword or symbol)
  • Tools — The Tools tool exposed by this server

Configuration and credentials

  • Node.js 16 or later - Rust and Cargo installed

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Cargo Doc's toolset — get_crate_doc, Parameters, crate_name and 4 more — is a fair guide to whether it matches your workflow. It is maintained by spacemeowx2; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Cargo Doc's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the cargo doc mcp server does with a few real requests.

Available tools

ToolWhat it does
get_crate_docGet crate's main documentation page for understanding overall concepts and usage
Parameters- project_path: Path to the Rust project (must be absolute path)
crate_nameName of the crate to get documentation for
list_symbolsList all symbols (structs, enums, traits, etc.) in a crate's documentation
search_docSearch within a crate's documentation
querySearch query (keyword or symbol)
ToolsThe Tools tool exposed by this server.

Configuration

  • Node.js 16 or later - Rust and Cargo installed

Example prompts to try

  • Use Cargo Doc to get crate doc.
  • Use Cargo Doc to Parameters.
  • Use Cargo Doc to crate name.

Frequently asked questions

Key features include retrieving documentation pages for crates, listing symbols within a crate's documentation, searching documentation, caching built paths for performance, and an MCP inspector for debugging.