Model Context Protocol (MCP) Rust SDK
LocalAbout Model Context Protocol (MCP) Rust SDK
Model Context Protocol (MCP) Rust SDK is a work-in-progress Rust library for building MCP clients and servers. It offers WebSocket and stdio transports, async support with Tokio, and typed message handling; it is not production-ready.
Key features
- 01MCP client and server library
- 02WebSocket and stdio transports
- 03Tokio async support
- 04Type-safe message handling
- 05Error handling and zero-copy serialization
Use cases
- 01Build an MCP client in Rust
- 02Implement an MCP server in Rust
- 03Connect over WebSocket or stdio
- 04Prototype MCP integrations with Tokio
MCP support
Implements MCP client and server functionality in Rust, including WebSocket and stdio transports. The SDK is explicitly marked as not ready for production use.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEModel Context Protocol (MCP) Rust SDK
⚠️ Warning: This SDK is currently a work in progress and is not ready for production use.
A Rust implementation of the Model Context Protocol (MCP), designed for seamless communication between AI models and their runtime environments.
Features
- 🚀 Full implementation of MCP protocol specification
- 🔄 Multiple transport layers (WebSocket, stdio)
- ⚡ Async/await support using Tokio
- 🛡️ Type-safe message handling
- 🔍 Comprehensive error handling
- 📦 Zero-copy serialization/deserialization
Installation
Add this to your Cargo.toml:
[dependencies]
mcp_sdk_rs = "0.1.0"
Quick Start
Client Example
use mcp_sdk_rs::{Client, transport::WebSocketTransport};
#[tokio::main]
async fn main() -> Result<(), Error> {
// Create a transport
let transport = WebSocketTransport::new(self.url.as_str())
.await
.map_err(|_| Error::Internal)?;
//Create mpsc channels for communication between the client and session
let (request_tx, request_rx): (UnboundedSender<Message>, UnboundedReceiver<Message>) =
tokio::sync::mpsc::unbounded_channel();
let (response_tx, response_rx): (UnboundedSender<Message>, UnboundedReceiver<Message>) =
tokio::sync::mpsc::unbounded_channel();
// Create and start the session
// Optionally pass an implementation of ClientHandler for custom handling of requests and notifications
let session = Session::new(Arc::new(transport), response_tx, request_rx, None);
session.start().await.map_err(|_| Error::Internal)?;
// Create the client and make requests, receive notifications etc
let client = Client::new(request_tx, response_rx);
let response = client.request(
"tools/call",
Some(json!({
"name": "methondName",
"arguments": json!({})
})),
)
.await?
}
Server Example
use mcp_sdk_rs::{Server, transport::StdioTransport};
#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
// Create a stdio transport
let (transport, _) = StdioTransport::new();
// Create and start the server
let server = Server::new(transport);
server.start().await?;
Ok(())
}
Transport Layers
The SDK supports multiple transport layers:
WebSocket Transport
- Ideal for network-based communication
- Supports both secure (WSS) and standard (WS) connections
- Built-in reconnection handling
stdio Transport
- Perfect for local process communication
- Lightweight and efficient
- Great for command-line tools and local development
Error Handling
The SDK provides comprehensive error handling through the Error type:
use mcp_sdk_rs::Error;
match result {
Ok(value) => println!("Success: {:?}", value),
Err(Error::Protocol(code, msg)) => println!("Protocol error {}: {}", code, msg),
Err(Error::Transport(e)) => println!("Transport error: {}", e),
Err(e) => println!("Other error: {}", e),
}
License
This project is licensed under the MIT License - see the LICENSE file for details.
Originally forked from https://github.com/Derek-X-Wang/mcp-rust-sdk.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.