Rust MCP SDK

Created By
rust-mcp-stacka year ago
A high-performance, asynchronous toolkit for building MCP servers and clients in Rust.
Overview

What is Rust MCP SDK?

Rust MCP SDK is a high-performance, asynchronous toolkit designed for building Model Context Protocol (MCP) servers and clients in Rust. It simplifies the development process by providing essential components for creating robust and reliable applications in the MCP ecosystem.

How to use Rust MCP SDK?

To use Rust MCP SDK, you can create an MCP server or client by defining server/client details, capabilities, and implementing custom handlers for processing MCP messages. The SDK provides examples and documentation to guide you through the setup process.

Key features of Rust MCP SDK?

  • High-performance asynchronous toolkit for MCP development.
  • Type-safe MCP schema objects and utilities for error minimization.
  • Support for both MCP servers and clients.
  • Detailed examples for quick start.

Use cases of Rust MCP SDK?

  1. Building a simple "Hello World" MCP server.
  2. Creating an MCP client that interacts with an existing MCP server.
  3. Developing complex applications that require reliable data handling and message processing.

FAQ from Rust MCP SDK?

  • Is Rust MCP SDK suitable for production use?

The project is currently under development and should be used at your own risk.

  • What transport methods are supported?

Currently, only Standard Input/Output (stdio) transport is supported, with Server-Sent Events (SSE) transport in progress.

  • Where can I find more examples?

You can find more examples in the examples directory.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
rust-mcp-stack
Star
44
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