MCP server for querying Rust crates from crates.io and docs.rs. Search crates, get info, versions, dependencies, and documentation.
MCP server for querying Rust crates from crates.io and docs.rs. Search crates, get info, versions, dependencies, and documentation. That is what the crates mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
The server publishes 5 tools. What each one is for:
search_crates — Find crates by nameget_crate_info — Get details about a crateget_crate_versions — List versionsget_crate_dependencies — Show dependenciesget_crate_documentation — Get docs from docs.rsSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Crates MCP's toolset — search_crates, get_crate_info, get_crate_versions and 2 more — is a fair guide to whether it matches your workflow. It is maintained by pato; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Crates MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| search_crates | Find crates by name |
| get_crate_info | Get details about a crate |
| get_crate_versions | List versions |
| get_crate_dependencies | Show dependencies |
| get_crate_documentation | Get docs from docs.rs |
**Option 2: Use binary**
```bash
# Build first
cargo build --release
# Add to config
{
"mcpServers": {
"crates": {
"command": "/path/to/crates-mcp/target/release/crates-mcp"
}
}
}Configuration as documented by the project. Restart the client after saving.
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.