Rust MCP Server

Created By
lha year ago
Model Context Protocol server for Rust development tools (clippy, rustfmt, cargo check, cargo test)
Overview

What is Rust MCP Server?

Rust MCP Server is a Model Context Protocol (MCP) server designed to provide essential Rust development tools such as syntax checking, linting, formatting, testing, and building of Rust projects through a standardized interface.

How to use Rust MCP Server?

To use the Rust MCP Server, clone the repository from GitHub, build the server, and integrate it with your development environment (e.g., Claude Code) to utilize its features via natural language commands.

Key features of Rust MCP Server?

  • cargo_check: Validates Rust code syntax and types.
  • cargo_clippy: Lints code and suggests improvements.
  • rustfmt: Formats code according to style guidelines.
  • cargo_test: Executes tests with detailed output.
  • cargo_build: Builds Rust projects in debug or release mode.

Use cases of Rust MCP Server?

  1. Real-time syntax validation during coding.
  2. Automatic linting and code improvement suggestions.
  3. Consistent code formatting across projects.
  4. Running tests to ensure code integrity.
  5. Building projects for deployment.

FAQ from Rust MCP Server?

  • What tools does the server support?

The server supports cargo_check, cargo_clippy, rustfmt, cargo_test, and cargo_build.

  • Is there a specific Rust version required?

Yes, the Rust toolchain must be installed, including rustc, cargo, clippy, and rustfmt.

  • Can it be integrated with IDEs?

Yes, it can be integrated with IDEs like Claude Code and VS Code for enhanced development experience.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
lh
Star
1
Language
Rust
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