search_cratesLABSCO SUMMARY
The crate question, answered from the registry.
Model knowledge of the Rust ecosystem goes stale between releases. This checks the registry instead: which versions exist now, what a crate pulls in, and what its current documentation says.
What it is
A lookup against crates.io and docs.rs. It finds crates by name, reports what a crate is and which versions exist, lists what it depends on, and pulls its documentation.
What you get
- Crates found by name
- The details of a crate
- The list of published versions
- A crate's dependencies
- Documentation from docs.rs
Requirements
A Rust toolchain — the server is built with cargo build --release and run as the resulting binary. It queries crates.io and docs.rs over the network.
Setup effort
Build from source — get the source and build it, then follow the steps on this page and add the configuration for your client
USE CASES
01
Choosing a crate for a job
Search on what you need, then read what each candidate actually is before it goes into Cargo.toml.
02
Checking a version before you pin it
List the published versions rather than assuming the one you remember is still current.
03
Seeing what a dependency drags in
Read the crate's dependencies before it becomes part of your build.
04
Writing code against an unfamiliar API
Pull the docs.rs documentation into the conversation so the calls come from the current interface.
5 tools
Listed in project docs. Your client may show a different list.
get_crate_infoget_crate_versionsget_crate_dependenciesget_crate_documentationBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Requires
cargo on PATH
Where it runs
Both documented setups run the server on your machine.
INSTALLATION
Connect your client
Get the source and build it, then follow the steps on this page and add the configuration for your client. This one is built from source rather than installed with a single command.
Server setup
TERMINAL
# Build and run
cargo build --release
cargo run --releaseMCP Clients
Claude Code — cargo run
CLAUDE CODE — CARGO RUN · JSON
{
"mcpServers": {
"crates": {
"command": "cargo",
"args": [
"run",
"--release"
],
"cwd": "<YOUR_PATH_TO_CRATES_MCP>"
}
}
}Claude Code — prebuilt binary
CLAUDE CODE — PREBUILT BINARY · JSON
{
"mcpServers": {
"crates": {
"command": "<YOUR_PATH_TO_CRATES_MCP>/target/release/crates-mcp"
}
}
}
