Rust Docs MCP Server

Created By
Govcrafta year ago
🦀 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.
Overview

What is Rust Docs MCP Server?

Rust Docs MCP Server is a tool designed to provide up-to-date documentation for Rust crates, preventing outdated code suggestions from AI coding assistants by fetching current crate documentation and using embeddings and LLMs for accurate context.

How to use Rust Docs MCP Server?

To use the server, you need to run it from the command line with the package ID specification for the target crate. Ensure you have an OpenAI API key set in your environment variables. The server will download the documentation and generate embeddings for the specified crate.

Key features of Rust Docs MCP Server?

  • Targeted documentation for individual Rust crates.
  • Semantic search capabilities using OpenAI's embedding model.
  • Caching of documentation and embeddings for faster subsequent launches.
  • Integration with AI coding assistants via the Model Context Protocol (MCP).

Use cases of Rust Docs MCP Server?

  1. Providing accurate API documentation for Rust crates to AI coding assistants.
  2. Enhancing the coding experience by reducing outdated suggestions.
  3. Supporting multiple crate instances for concurrent documentation access.

FAQ from Rust Docs MCP Server?

  • Can the server handle multiple crates at once?

Yes, multiple instances can be run concurrently for different crates.

  • Is an OpenAI API key required?

Yes, the server requires an OpenAI API key for generating embeddings and summarizing answers.

  • How does caching work?

The server caches documentation and embeddings in the user's XDG data directory to speed up future launches.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Govcraft
Star
93
Language
Rust
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

17 hours ago
Voyei

7 hours ago