MCP server for fetching Rust crate documentation via docs.rs RustDoc API
MCP server for fetching Rust crate documentation via docs.rs RustDoc API. That is what the mcp docsrs mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
Download the latest release for your platform from the Releases page:
Installation goes through your MCP client rather than a global install: point it at ghcr.io/vexxvakan/mcp-docsrs on a container image and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
The server publishes 11 tools. What each one is for:
Linux — The Linux tool exposed by this servermacOS — The macOS tool exposed by this serverWindows — The Windows tool exposed by this serverConfiguration — Configure the server using environment variables or command-line arguments:Crate — The Crate tool exposed by this servercrate_lookup — Retrieves a crate overview with its structure and public API surface from docs.rscrate_docs — The crate_docs tool exposed by this servercrate_find — Searches crates.io for matching crates and returns ranked results using fuzzy and partial name matchingSymbol — The Symbol tool exposed by this serversymbol_lookup — Retrieves structured symbol metadata for one symbol inside a cratesymbol_docs — Retrieves the full documentation body for one symbol inside a cratePlenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Docsrs's toolset — Linux, macOS, Windows and 8 more — is a fair guide to whether it matches your workflow. It is maintained by vexxvakan; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Linux | The Linux tool exposed by this server. |
| macOS | The macOS tool exposed by this server. |
| Windows | The Windows tool exposed by this server. |
| Configuration | Configure the server using environment variables or command-line arguments: |
| Crate | The Crate tool exposed by this server. |
| crate_lookup | Retrieves a crate overview with its structure and public API surface from docs.rs. |
| crate_docs | The crate_docs tool exposed by this server. |
| crate_find | Searches crates.io for matching crates and returns ranked results using fuzzy and partial name matching. |
| Symbol | The Symbol tool exposed by this server. |
| symbol_lookup | Retrieves structured symbol metadata for one symbol inside a crate. |
| symbol_docs | Retrieves the full documentation body for one symbol inside a crate. |
{
"mcpServers": {
"docsrs": {
"command": "docker",
"args": ["run", "-i", "--rm", "ghcr.io/vexxvakan/mcp-docsrs"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.