About Cratedocs MCP
Cratedocs MCP is an MCP server published by lnay in the Developer Tools category: an MCP server for rust crate docs.
The repository has 3 stars and 15 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.
Install
git clone https://github.com/lnay/cratedocs-mcpThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about Cratedocs MCP
Powered by Claude · Grounded in docs
Security checks
- ✓README presentThe repository ships documentation.
5 checks have not been run yet.
README
CrateDocs MCP
This is an MCP (Model Context Protocol) server that provides tools for Rust crate documentation lookup. It allows LLMs to look up documentation for Rust crates they are unfamiliar with.
Features
- Lookup crate documentation: Get general documentation for a Rust crate
- Search crates: Search for crates on crates.io based on keywords
- Lookup item documentation: Get documentation for a specific item (e.g., struct, function, trait) within a crate
Installation
git clone https://github.com/yourusername/cratedocs-mcp.git
cd cratedocs-mcp
cargo build --release
Running the Server
There are multiple ways to run the documentation server:
Using the Unified CLI
The unified command-line interface provides subcommands for all server modes:
# Run in STDIN/STDOUT mode
cargo run --bin cratedocs stdio
# Run in HTTP/SSE mode (default address: 127.0.0.1:8080)
cargo run --bin cratedocs http
# Run in HTTP/SSE mode with custom address
cargo run --bin cratedocs http --address 0.0.0.0:3000
# Enable debug logging
cargo run --bin cratedocs http --debug
Directly Testing Documentation Tools
You can directly test the documentation tools from the command line without starting a server:
# Get help for the test command
cargo run --bin cratedocs test --tool help
# Look up crate documentation
cargo run --bin cratedocs test --tool lookup_crate --crate-name tokio
# Look up item documentation
cargo run --bin cratedocs test --tool lookup_item --crate-name tokio --item-path sync::mpsc::Sender
# Look up documentation for a specific version
cargo run --bin cratedocs test --tool lookup_item --crate-name serde --item-path Serialize --version 1.0.147
# Search for crates
cargo run --bin cratedocs test --tool search_crates --query logger --limit 5
# Output in different formats (markdown, text, json)
cargo run --bin cratedocs test --tool search_crates --query logger --format json
cargo run --bin cratedocs test --tool lookup_crate --crate-name tokio --format text
# Save output to a file
cargo run --bin cratedocs test --tool lookup_crate --crate-name tokio --output tokio-docs.md
By default, the HTTP server will listen on http://127.0.0.1:8080/sse.
Available Tools
The server provides the following tools:
1. lookup_crate
Retrieves documentation for a specified Rust crate.
Parameters:
crate_name(required): The name of the crate to look upversion(optional): The version of the crate (defaults to latest)
Example:
{
"name": "lookup_crate",
"arguments": {
"crate_name": "tokio",
"version": "1.28.0"
}
}
2. search_crates
Searches for Rust crates on crates.io.
Parameters:
query(required): The search querylimit(optional): Maximum number of results to return (defaults to 10, max 100)
Example:
{
"name": "search_crates",
"arguments": {
"query": "async runtime",
"limit": 5
}
}
3. lookup_item
Retrieves documentation for a specific item in a crate.
Parameters:
crate_name(required): The name of the crateitem_path(required): Path to the item (e.g., 'std::vec::Vec')version(optional): The version of the crate (defaults to latest)
Example:
{
"name": "lookup_item",
"arguments": {
"crate_name": "serde",
"item_path": "serde::Deserialize",
"version": "1.0.160"
}
}
Implementation Notes
- The server includes a caching mechanism to prevent redundant API calls for the same documentation
- It interfaces with docs.rs for crate documentation and crates.io for search functionality
- Results are returned as plain text/HTML content that can be parsed and presented by the client
MCP Protocol Integration
This server implements the Model Context Protocol (MCP) which allows it to be easily integrated with LLM clients that support the protocol. For more information about MCP, visit the MCP repository.
License
MIT License
README copy captured when this server was indexed; it may lag the repository. The original is authoritative.