Rust Docs

Download a pre-built binary from GitHub Releases for your platform, or build from source using cargo.

# Build from source
git clone https://github.com/Govcraft/rust-docs-mcp-server.git
cd rust-docs-mcp-server
cargo build --release
# Binary will be at: ./target/release/rustdocs_mcp_server

Copy or symlink the compiled binary to a directory on your PATH so MCP clients can launch it by name.

cp target/release/rustdocs_mcp_server /usr/local/bin/

The server requires OPENAI_API_KEY at runtime. Set it in your shell environment or provide it directly in the MCP client configuration.

export OPENAI_API_KEY="sk-...your-key-here..."

Each server instance targets one crate and version. Add a block to your MCP client config for every crate you want documentation for. The crate name and version are passed as command arguments.

{
  "mcpServers": {
    "rust-docs-serde": {
      "command": "rustdocs_mcp_server",
      "args": ["serde@^1.0"],
      "env": {
        "OPENAI_API_KEY": "sk-your-key-here"
      }
    },
    "rust-docs-tokio": {
      "command": "rustdocs_mcp_server",
      "args": ["tokio"],
      "env": {
        "OPENAI_API_KEY": "sk-your-key-here"
      }
    }
  }
}

On the first launch for a crate, the server fetches and indexes all documentation, which may take a minute or two. Subsequent starts use the cache at ~/.local/share/rustdocs-mcp-server/ and are much faster.

If the crate has feature flags that affect its API, pass them with the -F flag so the documentation index includes those feature-gated items.

rustdocs_mcp_server "[email protected]" -F rustls-tls,json