get
Show documentation for a Rust item by path.
path必填
rs.ferritin由 ferritin.rs 发布官方发布者v2026.7.21更新于 Oct 24, 2026
Search and read Rust documentation for the standard library and any crate on crates.io
一个远程 MCP 服务器,让助手查阅并搜索 Rust 标准库和 crates.io 各 crate 的文档。
Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/rs.ferritin%2Frustdoc/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。把它添加到你客户端的 mcpServers 配置中。
{
"mcpServers": {
"ferritin-rust-documentation": {
"type": "http",
"url": "https://ferritin.rs/mcp"
}
}
}[ci] [codecov] [crates.io version badge]
A terminal-based Rust documentation viewer
Ferritin reads rustdoc JSON output to display Rust documentation directly in your terminal. It supports local workspace crates, standard library documentation, and crates from crates.io, with search functionality and modern terminal features including mouse support, syntax highlighting, and clickable links.
rust-docs-json rustup component)Prebuilt binaries skip compilation and are available for x86_64/aarch64 macOS, x86_64 Linux, and x86_64 Windows.
If you have cargo-binstall, it reads the release metadata and installs the right binary for your platform:
Otherwise, the installer scripts detect your platform, download the matching binary, and
place it in ~/.cargo/bin:
macOS and Linux:
Windows (PowerShell):
Both of the above always install the most recent release. You can also pick a specific version or download archives directly from the releases page.
To build from source (or for a platform without a prebuilt binary):
To view documentation for std, core, and alloc:
Local crate documentation requires a nightly toolchain:
Note: There is a relationship between ferritin's version and the nightly toolchain version. Ferritin supports a range of recent rustdoc JSON format versions, and if your nightly generates a newer format, ferritin will make a best effort at parsing it.
Launch the interactive browser:
Once running, use h or ? to see available keybindings. Basic navigation:
g - go to an item by path (e.g., std::vec::Vec)s - search (Tab to toggle between current crate and all crates)l - list available cratesView documentation for a specific item:
Search for items:
List available crates in your workspace:
Ferritin auto-detects how to render: ANSI colors on a terminal, plain text when
piped, and a compact markdown-flavored format under a coding agent. Override it
with --format <tty|plain|agent|json>. --format json emits a structured
representation — of the resolved item for get, or of the results for
search/list — for scripting and programmatic consumers:
(The JSON shape is still settling as the library API evolves; a published JSON Schema is planned.)
Ferritin keeps its caches under a single directory — $FERRITIN_HOME if set,
else $XDG_CACHE_HOME/ferritin, else ~/.cache/ferritin. Everything in it is
reconstructible (fetched or derived), so it is always safe to delete:
docs/{crate}/{version}/{format-version}.json, with derived binary caches
beside it (an rkyv archive for fast partial loads, and a .index file
generated lazily on first search)crate-names/) used for
version resolution and typeahead, and per-crate version lookups
(crates-io-versions/){rustc sysroot}/share/doc/rust/json/ if availabletarget/doc/, not the shared cacheEarlier versions cached under $CARGO_HOME/rustdoc-json; a cache found there
is migrated automatically on first run.
ferritin serve (the opt-in serve/acme features; not present in
distributed binaries) is configured 12-factor style:
Development-only knobs (not part of the stable interface): FERRITIN_TEST_MODE
(normalized snapshot-test output), FERRITIN_REINDEX (rebuild search indexes
in memory, bypassing the disk cache), and the search-scoring probes
FERRITIN_NAME_WEIGHT, FERRITIN_ANCESTOR_WEIGHTS, and
FERRITIN_NAME_PREFIX_COUNT.
Ferritin is at version 0.x and actively used by the author as a primary documentation interface. It's ready for general use, though the output format should be considered unstable and may change between versions.
If you're scripting against ferritin's output, be aware that the text format may change. Pin to a specific version or be prepared to update your scripts.
Ferritin is developed primarily on Unix-like systems and is also tested on Windows, where both the CLI and interactive TUI work (prebuilt x86_64 Windows binaries are provided). If you encounter issues on any platform, please open an issue or pull request.
Ferritin was originally developed to support the rustdoc-mcp MCP server, which provides Rust documentation access for Claude Code and other MCP clients.
来源:README.md,提交 3770aa6
Show documentation for a Rust item by path.
path必填Search for items within a crate's documentation, or — without a crate — discover which crate to use.
cratequery必填已满足适用检查项的 100%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
cargo binstall ferritincurl --proto '=https' --tlsv1.2 -LsSf https://github.com/jbr/ferritin/releases/download/ferritin-latest/ferritin-installer.sh | shpowershell -c "irm https://github.com/jbr/ferritin/releases/download/ferritin-latest/ferritin-installer.ps1 | iex"cargo install ferritinrustup component add rust-docs-jsonrustup toolchain install nightlyferritin -iferritin get std::vec::Vecferritin get serde::Serializeferritin search "hash map"ferritin search --crate tokio "spawn"ferritin listferritin get std::vec::Vec --format json