rust-mcp-sdk MCPサーバー
コミット 2026年11月9日asyncトランスポート、マクロ、OAuthサポートを備えたRustによるMCP serverおよびclientの構築。
別名 rust-mcp-stack/rust-mcp-sdk
- スター
- 200
- ツール
- —
- ダウンロード数(30日間)
- —
- 最新バージョン
- —
- 最終コミット
- 2026年11月9日
- ライセンス
- MIT
rust-mcp-sdk MCPとは
asyncトランスポート、マクロ、OAuthサポートを備えたRustによるMCP serverおよびclientの構築。
プロジェクトのREADMEから生成された概要
rust-mcp-sdk MCP server について
この非同期Rustツールキットの主な目的は、高性能なModel Context Protocol serverおよびclientを開発することです。開発者は、厳格なテストを通じて完全な準拠を保証しながら、MCP 2026-07-28ステートレスプロトコルを実装するために必要なコンポーネントを利用できます。このSDKは、Stdio、Streamable HTTP、および後方互換性のあるSSEを含む複数のトランスポート方式をサポートしており、ローカルおよびリモートの両方のデプロイに適しています。
エンジニアは、AxumまたはActixバックエンドを使用してツールキットを既存のアプリケーションに統合したり、BYO-serverアプローチを使用したりできます。このライブラリは、mcp_tool、mcp_resource、mcp_promptなどの手続き型マクロを通じて開発を簡素化し、ユーザーがプロトコルの実装ではなくアプリケーションロジックに集中できるようにします。また、Keycloak、WorkOS、Scalekitなどのプロバイダーを介したOAuth認証や、serverからclientへの入力リクエストに対するリクエスト中ターンアラウンド機能などの高度な機能も含まれています。
できること
- 1ローカルMCP serverの構築標準入出力経由で通信する、最小限のツールベースのserverを作成できます。
- 2リモートHTTP serverのデプロイAxumまたはActix webフレームワークを使用して、リモートクライアントからアクセス可能なステートレスなMCP serverをホストできます。
- 3OAuthによるserverの保護確立されたIDプロバイダーを使用して、MCP serverに安全な認証を実装できます。
プロジェクトの README から作成されています。すべてのユースケースは、その引用と照らし合わせて確認されています。
自動チェック
実行日 2026年11月14日完全なレポート →まだ検証されていません。サーバーには80点のスコア、重大な問題がないこと、および検証に必要な十分なデータが必要です。 チェックの仕組み · 点数を上げるための改善点
- ソースリポジトリがリンクされており、アクセス可能rust-mcp-stack/rust-mcp-sdk is public and reachablegithub.com/rust-mcp-stack/rust-mcp-sdk ↗合格
- パッケージがこのリポジトリをソースとして指定未チェック
- ビルドの来歴 (Sigstore 証明)未チェック
- オープンソースライセンス (OSI)MITspdx.org/licenses/MIT.html ↗合格
- 過去1年以内にコミットまたはリリースありLast commit or release 2026-11-09github.com/rust-mcp-stack/rust-mcp-sdk ↗合格
- OpenSSF Scorecard未チェック
- パッケージ名が有名なパッケージに酷似していない未チェック
- パッケージおよびその依存関係に重大な勧告なし未チェック
- モデルへの隠れた指示がない0 tool descriptions and the README read; no override phrases, credential paths or hidden characters合格
- 破壊的なツールがラベル付けされている未チェック
- リモートエンドポイントが MCP ハンドシェイクに応答未チェック
README
GitHubで見るA high-performance, asynchronous Rust toolkit for building MCP servers and clients.
📖 Documentation · Tutorials · Examples · Upgrade Guide · Changelog Contributing · Report a bug · Request a Feature
🥇 Tier 1 SDK: passes 100% of scored conformance scenarios, and the official MCP conformance tool's tier-check reports Tier 1 under SEP-1730. Tier-check runs · release reports
✅ This SDK fully implements the MCP 2026-07-28 stateless protocol and passes 100% of official MCP conformance tests.
rust-mcp-sdk provides the necessary components for developing both servers and clients in the MCP ecosystem. It leverages the rust-mcp-schema crate for type-safe schema objects and includes powerful procedural macros.
Focus on your application logic, rust-mcp-sdk handles the protocol, transports, and the rest.
Version notice: This is rust-mcp-sdk 2.x, implementing the new MCP 2026-07-28 (stateless) specification.
For the previous MCP 2025-11-25 specification, use rust-mcp-sdk 1.x.
See the upgrade guide to migrate from 1.x to 2.0.
Version matrix:
| SDK version | Protocol | Branch |
|---|---|---|
| 2.0 | MCP 2026-07-28 (stateless) | main |
| 1.x (LTS) | MCP 2025-11-25 | release-1.x |
Upgrading? See the upgrade guide.
Key Features
- ✅ Latest MCP protocol specification supported: 2026-07-28
- 🥇 Tier 1 SDK - official MCP conformance tool's
tier-checkreports Tier 1 under SEP-1730. see tier-check runs· - ✅ 100% MCP Conformance - passes all official client (254/254) and server (40/40) conformance tests
- ✅ Transports: Stdio, Streamable HTTP, and backward-compatible SSE support
- ✅ Framework Agnostic: Axum, Actix, and BYO Server integrations
- ✅ MRTR (Mid-Request Turn-Around) for server→client input requests
- ✅ Response cache (SEP-2549) with principal-scoped privacy + auto-pagination
- ✅ Per-request
_metawithRequestContext - ✅ Multi-client concurrency
- ✅ DNS Rebinding Protection
- ✅ Message Observer (Telemetry & Monitoring)
- ✅ HTTP Health Checks (for load balancers & container orchestration)
- ✅ OAuth Authentication for MCP Servers
- ✅ Remote Oauth Provider
- Keycloak Provider (via rust-mcp-extra)
- WorkOS Authkit Provider (via rust-mcp-extra)
- Scalekit Authkit Provider (via rust-mcp-extra)
- ✅ Remote Oauth Provider
- ✅ OAuth Authentication for MCP Clients (metadata discovery, CIMD, PKCE, token refresh, pluggable storage)
- ✅ Issuer-bound credentials (SEP-2352), strict
issvalidation (SEP-2468)
Table of Contents
- Quick Start
- Minimal MCP Server (Stdio)
- Minimal MCP Server (Streamable HTTP)
- Minimal MCP Client (Stdio)
- Usage Examples
- Macros
- Authentication
- HTTP Server Backends (Axum & Actix)
- Cargo features
- Handler Traits
- Message Observer (Telemetry & Monitoring)
- Health Check Endpoint
- Contributing
- Development
- License
Quick Start
Add to your Cargo.toml:
[dependencies]
rust-mcp-sdk = "2.0.0" # Check crates.io for the latest version
Minimal MCP Server (Stdio)
use async_trait::async_trait;
use rust_mcp_sdk::{
error::SdkResult, macros, mcp_icon,
mcp_server::{server_runtime, McpServerOptions, ServerHandler},
schema::*,
McpServer, RequestContext, ServerDetails, StdioTransport, ToMcpServerHandler,
TransportOptions,
};
// Define an MCP tool
#[macros::mcp_tool(name = "say_hello", description = "returns \"Hello from Rust MCP SDK!\" message")]
#[derive(Debug, ::serde::Deserialize, ::serde::Serialize, macros::JsonSchema)]
pub struct SayHelloTool {}
// Define a custom handler
#[derive(Default)]
struct HelloHandler;
#[async_trait]
impl ServerHandler for HelloHandler {
async fn handle_list_tools_request(
&self,
_request: Option<PaginatedRequestParams>,
_context: &RequestContext,
_runtime: std::sync::Arc<dyn McpServer>,
) -> std::result::Result<ListToolsResult, RpcError> {
Ok(ListToolsResult {
tools: vec![SayHelloTool::tool()],
meta: None,
next_cursor: None,
cache_scope: Default::default(),
result_type: "complete".to_string(),
ttl_ms: 0,
})
}
async fn handle_call_tool_request(
&self,
params: CallToolRequestParams,
_context: &RequestContext,
_runtime: std::sync::Arc<dyn McpServer>,
) -> std::result::Result<ServerResult, CallToolError> {
if params.name == "say_hello" {
Ok(ServerResult::CallToolResult(CallToolResult {
content: vec![ContentBlock::TextContent(TextContent::new(
"Hello from Rust MCP SDK!".to_string(),
None,
None,
))],
is_error: None,
meta: None,
result_type: "complete".to_string(),
}))
} else {
Err(CallToolError::unknown_tool(params.name))
}
}
}
#[tokio::main]
async fn main() -> SdkResult<()> {
let server_details = ServerDetails {
server_info: Implementation {
name: "hello-rust-mcp".into(),
version: "0.1.0".into(),
title: Some("Hello World MCP Server".into()),
description: Some("A minimal Rust MCP server".into()),
icons: vec![mcp_icon!(
src = "https://raw.githubusercontent.com/rust-mcp-stack/rust-mcp-sdk/main/assets/rust-mcp-icon.png",
mime_type = "image/png",
sizes = ["128x128"],
theme = "light"
)],
website_url: Some("https://github.com/rust-mcp-stack/rust-mcp-sdk".into()),
},
capabilities: ServerCapabilities {
tools: Some(ServerCapabilitiesTools { list_changed: None }),
..Default::default()
},
instructions: None,
meta: None,
};
let transport = StdioTransport::new(TransportOptions::default())?;
let handler = HelloHandler::default().to_mcp_server_handler();
let server = server_runtime::create_server(McpServerOptions {
server_details,
transport,
handler,
message_observer: None,
});
server.start().await
}
HTTP Server Backends (Axum & Actix)
Creating a Streamable HTTP MCP server in rust-mcp-sdk allows multiple clients to connect simultaneously with no additional setup. The setup is nearly identical to the stdio example , the only difference is which HTTP backend crate you install and which function you call to create the server.
Post only - the 2026-07-28 protocol is stateless. GET and DELETE endpoints return 405 Method Not Allowed.
Axum Backend (rust-mcp-axum)
Add rust-mcp-axum to your dependencies and use create_axum_server() with AxumServerOptions.
use async_trait::async_trait;
use rust_mcp_axum::{create_axum_server, AxumServerOptions};
use rust_mcp_sdk::{
error::SdkResult, macros,
mcp_server::ServerHandler, schema::*,
};
// ... (define SayHelloTool and HelloHandler as shown above)
#[tokio::main]
async fn main() -> SdkResult<()> {
let server_details = ServerDetails { /* ... */ };
let handler = HelloHandler::default().to_mcp_server_handler();
let server = create_axum_server(
server_details,
handler,
AxumServerOptions {
host: "127.0.0.1".to_string(),
..Default::default()
},
);
server.start().await?;
Ok(())
}
Actix-web Backend (rust-mcp-actix)
Add rust-mcp-actix to your dependencies and use create_actix_server() with ActixServerOptions.
use rust_mcp_actix::{create_actix_server, ActixServerOptions};
use rust_mcp_sdk::{
error::SdkResult,
mcp_server::ServerHandler, schema::*,
};
// ... (define SayHelloTool and HelloHandler as shown above)
#[tokio::main]
async fn main() -> SdkResult<()> {
let server_details = ServerDetails { /* ... */ };
let handler = HelloHandler::default().to_mcp_server_handler();
let server = create_actix_server(
server_details,
handler,
ActixServerOptions {
host: "127.0.0.1".to_string(),
..Default::default()
},
);
server.start().await?;
Ok(())
}
BYO-server: Embed MCP in your Existing App
Both backends support a BYO-server (Bring Your Own Server) mode, letting you mount MCP endpoints onto a router or app you already control - no need to hand over the server lifecycle.
| Backend | Function | Docs |
|---|---|---|
| Axum | mcp_routes(state, &mount_opts, http_handler) |
rust-mcp-axum README |
| Actix-web | mcp_scope(state, http_handler, &mount_opts) |
rust-mcp-actix README |
Custom HTTP Framework Integrations
The SDK is completely framework-agnostic. If you are using a different HTTP framework (like Rocket, Salvo, or Warp), you can build a custom integration by adapting your framework's native Request/Response types to the SDK's core HTTP handling logic.
See the Custom HTTP Framework Integration Guide for architectural details.
AxumServerOptions
Axum server is highly customizable through AxumServerOptions:
let server = create_axum_server(
server_details,
handler.to_mcp_server_handler(),
AxumServerOptions {
host: "127.0.0.1".to_string(),
port: 8080,
auth: Some(Arc::new(auth_provider)), // enable authentication
health_endpoint: Some("/health".into()), // health check
sse_support: true, // backward-compat SSE
..Default::default()
},
);
server.start().await?;
Security Considerations
- DNS rebinding protection is enabled by default. If
allowed_hostsis not set, it auto-derives fromhost:port. - When running locally, bind only to localhost (127.0.0.1 / localhost) rather than all network interfaces (0.0.0.0)
- Use TLS/HTTPS for production deployments
Following is implementation of an MCP client that starts the @modelcontextprotocol/server-everything server, discovers the server's capabilities, lists available tools, and calls a tool.
use async_trait::async_trait;
use rust_mcp_sdk::{
error::SdkResult,
mcp_client::{client_runtime, ClientHandler, McpClientOptions},
schema::*,
ClientDetails, McpClient, StdioTransport, ToMcpClientHandler, TransportOptions,
};
pub struct MyClientHandler;
#[async_trait]
impl ClientHandler for MyClientHandler {
// Override handler methods as needed.
// See: crates/rust-mcp-sdk/src/mcp_handlers/mcp_client_handler.rs
}
#[tokio::main]
async fn main() -> SdkResult<()> {
let client_details = ClientDetails {
client_info: Implementation {
name: "simple-rust-mcp-client".into(),
version: "0.1.0".into(),
description: None,
icons: vec![],
title: None,
website_url: None,
},
capabilities: ClientCapabilities::default(),
};
let transport = StdioTransport::create_with_server_launch(
"npx",
vec!["-y".to_string(), "@modelcontextprotocol/server-everything@latest".to_string()],
None,
TransportOptions::default(),
)?;
let handler = MyClientHandler {};
let client = client_runtime::create_client(McpClientOptions::new(
client_details,
transport,
handler.to_mcp_client_handler(),
));
client.clone().start().await?;
// Discover the server
let discover = client.request_discover(Default::default()).await?;
println!("Supported protocol versions: {:?}", discover.supported_versions);
// List tools
let tools = client.request_tool_list(None).await?.tools;
tools.iter().enumerate().for_each(|(i, tool)| {
println!(" {}. {} : {}", i + 1, tool.name, tool.description.unwrap_or_default());
});
// Call a tool (supports MRTR auto-retry)
let result = client.call_tool(CallToolRequestParams {
name: "say_hello".to_string(),
arguments: None,
input_responses: None,
request_state: None,
meta: RequestMetaObject::default(),
}).await?;
client.shut_down().await?;
Ok(())
}
Usage Examples
For more examples (stdio, Streamable HTTP, clients, auth, etc.), see the examples/ directory.
👉 For step-by-step tutorials (server, client, HTTP deployment, OAuth, and more), see the documentation site.
See the hello-world-mcp-server-stdio example running in the MCP Inspector:
Macros
Enable with the macros feature.
mcp_tool
Generate a Tool from a struct, with metadata (icons, hints, etc.).
#[mcp_tool(
name = "write_file",
title = "Write File Tool",
description = "Create or overwrite a file with new content.",
destructive_hint = false, idempotent_hint = false, open_world_hint = false, read_only_hint = false,
meta = r#"{ "key": "value" }"#,
icons = [(src = "https://website.com/write.png", mime_type = "image/png", sizes = ["128x128"], theme = "light")]
)]
#[derive(rust_mcp_macros::JsonSchema)]
pub struct WriteFileTool {
/// The target file's path for writing content.
pub path: String,
/// The string content to be written to the file
pub content: String,
}
tool_box!()
Automatically generates an enum based on the provided list of tools.
tool_box!(GreetingTools, [SayHelloTool, SayGoodbyeTool]);
let tools: Vec<Tool> = GreetingTools::tools();
mcp_elicit()
Generates type-safe elicitation (Form or URL mode) for user input.
#[mcp_elicit(message = "Please enter your info", mode = form)]
#[derive(JsonSchema)]
pub struct UserInfo {
#[json_schema(title = "Name", min_length = 5, max_length = 100)]
pub name: String,
#[json_schema(title = "Email", format = "email")]
pub email: Option<String>,
#[json_schema(title = "Age", minimum = 15, maximum = 125)]
pub age: i32,
#[json_schema(title = "Tags")]
pub tags: Vec<String>,
}
◾ mcp_resource()
A procedural macro attribute that generates utility methods to create fully populated Resource instances from compile-time metadata , usually used for exposing static assets like files, images, or documents. Also generates a RESOURCE_URI associated constant, usable in match patterns, and a resource_mime_type() accessor.
📝 For complete documentation, example usage, and a list of all available attributes, please refer to https://crates.io/crates/rust-mcp-macros.
◾ mcp_resource_template()
A procedural macro attribute that generates utility methods to create fully populated ResourceTemplate instances from compile-time metadata for exposing parameterized server resources. Also generates a RESOURCE_URI_TEMPLATE associated constant, usable in match patterns, and a resource_template_mime_type() accessor.
📝 For complete documentation, example usage, and a list of all available attributes, please refer to https://crates.io/crates/rust-mcp-macros.
◾ mcp_prompt()
A procedural macro attribute that generates utility methods to create fully populated Prompt instances from compile-time metadata, and , when the optional messages attribute is provided , to parse request arguments (from_arguments) and render them into a GetPromptResult (render). Struct fields become typed prompt arguments (String = required, Option<String> = optional, String + default = fallback), the prompts/get handler itself is left to the user.
📝 For complete documentation, example usage, and a list of all available attributes, please refer to https://crates.io/crates/rust-mcp-macros.
◾ mcp_icon!()
A convenient icon builder for implementations and tools, offering full attribute support including theme, size, mime, and more.
example usage:
let icon: crate::schema::Icon = mcp_icon!(
src = "http://website.com/icon.png",
mime_type = "image/png",
sizes = ["64x64"],
theme = "dark"
);
Authentication
MCP servers can verify tokens issued by other systems, integrate with external identity providers, or manage the entire authentication process.
RemoteAuthProvider
RemoteAuthProvider enables authentication with identity providers that support Dynamic Client Registration (DCR), letting MCP clients auto-register and obtain credentials.
OAuthProxy
OAuthProxy enables authentication with OAuth providers that don't support DCR.
Cargo Features
Available Features
server: Activates MCP server capabilitiesclient: Activates MCP client capabilitiesmacros: Procedural macros for Tool, Elicit, Resource structuressse: Server-Sent Events (SSE) transportstreamable-http: Streamable HTTP transportstdio: Standard input/output (stdio) transportauth: OAuth authentication support for MCP serverstls-no-provider: TLS without a crypto provider
Default Features
All features are enabled by default:
[dependencies]
rust-mcp-sdk = "2.0.0"
Using Only the Server Features
[dependencies]
rust-mcp-sdk = { version = "2.0.0", default-features = false, features = ["server", "macros", "stdio"] }
Using Only the Client Features
[dependencies]
rust-mcp-sdk = { version = "2.0.0", default-features = false, features = ["client", "stdio"] }
Handler Traits
Choosing Between ServerHandler and ServerHandlerCore
- ServerHandler: Recommended. Default implementations for all MCP messages. Override only what you need.
- ServerHandlerCore: Full control over request/notification/error dispatch.
Note: Use server_runtime::create_server() or server_runtime_core::create_server() depending on which handler you implement.
Choosing Between ClientHandler and ClientHandlerCore
Same principles apply on the client side: use client_runtime::create_client() with ClientHandler, or client_runtime_core::create_client() with ClientHandlerCore.
Message Observer (Telemetry & Monitoring)
Implement McpObserver to intercept all incoming and outgoing MCP messages for telemetry, logging, debugging, or monitoring.
let server = server_runtime::create_server(McpServerOptions {
server_details,
transport,
handler: handler.to_mcp_server_handler(),
message_observer: Some(SimpleServerObserver::new()),
});
rust-mcp-sdk MCPのよくある質問
rust-mcp-sdkとは何ですか?
MCP serverおよびclientを構築するための、高性能で非同期なRust用ツールキットです。プロトコル、トランスポート、スキーマ型を処理します。
rust-mcp-sdkはどのトランスポートをサポートしていますか?
Stdio、Streamable HTTP、および後方互換性のあるSSEトランスポートをサポートしています。
rust-mcp-sdkはどのMCPプロトコルバージョンを実装していますか?
Version 2.xはMCP 2026-07-28のステートレス仕様を実装しており、version 1.xはMCP 2025-11-25を対象としています。
rust-mcp-sdkはOAuth認証をサポートしていますか?
はい、PKCE、トークンリフレッシュ、およびKeycloakなどのリモートプロバイダーを含む、MCP serverとclientの両方のOAuth認証を提供します。
rust-mcp-sdkをAxumやActixで使用できますか?
はい、AxumやActixバックエンドとのフレームワークに依存しない統合に加え、既存のアプリケーションへのMCPの組み込みも可能です。