Rust Docs MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Rust Docs MCP Server?

Rust Docs MCP Server is an MCP (Model Context Protocol) server that provides access to Rust documentation from docs.rs, enabling AI tools to search for documentation, type information, feature flags, version numbers, and symbol definitions/source code.

how to use Rust Docs MCP Server?

To use the Rust Docs MCP Server, clone the repository, install dependencies using Bun, build the server, and run it either in development mode or as a built server. Configure your MCP client to connect to this server for documentation access.

key features of Rust Docs MCP Server?

  • Search for crates on docs.rs
  • Retrieve documentation for specific crates and versions
  • Access type information (structs, enums, traits, etc.)
  • Get feature flags for crates
  • List available versions for crates
  • Fetch source code for specific items
  • Search for symbols within crates

use cases of Rust Docs MCP Server?

  1. Assisting developers in finding Rust crate documentation quickly.
  2. Providing type information for better code understanding and development.
  3. Enabling AI tools to interact with Rust documentation seamlessly.

FAQ from Rust Docs MCP Server?

  • What is the Model Context Protocol?

The Model Context Protocol (MCP) is a protocol that allows tools to communicate and access contextual information from servers like this one.

  • Is the server free to use?

Yes! The Rust Docs MCP Server is open-source and free to use.

  • What technologies are used in this project?

The server is built using TypeScript and requires Bun for development.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
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.

8 hours ago