Gives your AI agent crate search, documentation, dependency analysis, download stats, and security auditing to make informed decisions about Rust
Most knowledge and memory work still happens through a UI a human drives. Cratesio MCP MCP server moves it into the conversation instead. Gives your AI agent crate search, documentation, dependency analysis, download stats, and security auditing to make informed decisions about Rust dependencies.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
The server publishes 14 tools. What each one is for:
search_crates — Search for crates by name or keywordsget_crate_info — Detailed crate metadata (description, links, stats)get_crate_versions — Version history with release dates and download countsget_crate_version — Detailed metadata for a specific versionget_crate_readme — README content for a crate versionget_crate_features — Feature flags and their sub-feature activationsget_crate_docs — Browse documentation structure from docs.rsget_doc_item — Full docs for a specific item (fn, struct, trait)search_docs — Search for items by name within a crate's docsget_dependencies — Dependencies for a specific versionget_reverse_dependencies — Crates that depend on a given crateaudit_dependencies — Check deps against OSV.dev vulnerability databasePlenty 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. Cratesio MCP's toolset — search_crates, get_crate_info, get_crate_versions and 11 more — is a fair guide to whether it matches your workflow. It is maintained by joshrotenberg; 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 |
|---|---|
| search_crates | Search for crates by name or keywords |
| get_crate_info | Detailed crate metadata (description, links, stats) |
| get_crate_versions | Version history with release dates and download counts |
| get_crate_version | Detailed metadata for a specific version |
| get_crate_readme | README content for a crate version |
| get_crate_features | Feature flags and their sub-feature activations |
| get_crate_docs | Browse documentation structure from docs.rs |
| get_doc_item | Full docs for a specific item (fn, struct, trait) |
| search_docs | Search for items by name within a crate's docs |
| get_dependencies | Dependencies for a specific version |
| get_reverse_dependencies | Crates that depend on a given crate |
| audit_dependencies | Check deps against OSV.dev vulnerability database |
| get_downloads | Download statistics and trends |
| get_version_downloads | Daily download stats for a specific version |
{
"mcpServers": {
"cratesio-mcp": {
"type": "http",
"url": "https://cratesio-mcp.fly.dev/"
}
}
}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.