MCP.so
ログイン

Rust Docs MCP Server

@Govcraft

基本情報

カテゴリ

メモリとナレッジ

ライセンス

MIT

トランスポート

stdio

作者

Govcraft

Rust Docs MCP Server について

🦀 Prevents outdated Rust code suggestions from AI assistants. This MCP server fetches current crate docs, uses embeddings/LLMs, and provides accurate context via a tool call.

Rust Docs MCP Server の設定

標準の設定はありません

このサーバーの README には解析可能な MCP 設定ブロックが含まれていません。インストール手順はリポジトリをご確認ください。

リポジトリ

Rust Docs MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Rust Docs MCP Server?

Rust Docs MCP Server is an MCP server that fetches documentation for a specified Rust crate, generates embeddings, and provides an MCP tool to answer questions about the crate based on the documentation context. It is designed for AI-powered coding assistants (such as Cursor, Cline, Roo Code) to access current, crate-specific API documentation, improving the accuracy of generated Rust code.

How to use Rust Docs MCP Server?

Install by downloading the pre-compiled binary for your OS from the GitHub Releases page (or build from source with the Rust Toolchain). Set the OPENAI_API_KEY environment variable. Run from the command line with a package ID specification (e.g., rustdocs_mcp_server serde@^1.0), optionally adding features with -F. The server communicates via stdio and exposes a tool query_rust_docs and a resource crate://<crate_name>. On first run for a new crate/version/feature set, it downloads docs and generates embeddings (then caches them). Subsequent launches use the cache.

Key features of Rust Docs MCP Server

  • Targets a single Rust crate per server instance.
  • Supports specifying required crate features for documentation generation.
  • Uses OpenAI text-embedding-3-small for semantic search.
  • Uses OpenAI gpt-4o-mini-2024-07-18 for LLM summarization.
  • Caches documentation and embeddings in the XDG data directory.
  • Runs as a standard MCP server over stdio.

Use cases of Rust Docs MCP Server

  • AI assistant generates code using the latest API of a crate like serde or tokio.
  • A developer configures multiple server instances for different crates (e.g., reqwest and async-stripe).
  • An LLM queries crate-specific documentation before writing code, reducing outdated suggestions.
  • Teams ensure generated Rust code aligns with current crate versions and feature flags.

よくある質問

1

What is Rust Docs MCP Server?

It is an MCP server that provides an AI assistant with up-to-date, crate-specific documentation via semantic search and LLM summarization.

2

How can I use it with multiple crates?

Run multiple server instances concurrently, each targeting a different crate (using different package ID specifications). Configure them in your MCP client (e.g., Roo Code or Claude Desktop) with separate entries.

3

What are the prerequisites?

An OpenAI API key (set as `OPENAI_API_KEY` environment variable) and network access to download crate dependencies and interact with the OpenAI API.

4

How much does embedding generation cost?

Typically fractions of a US penny per crate. For example, a large crate like `async-stripe` with over 5000 documentation pages cost $0.18 USD during testing.

5

How does caching work?

Cached documentation and embeddings are stored in `~/.local/share/rustdocs-mcp-server/<crate_name>/<version>/<features_hash>/` using `bincode`. Different version requirements and feature sets are cached separately. If the cache is missing or corrupted, the server regenerates automatically.

コメント

「メモリとナレッジ」の他のコンテンツ