Is this SDK production‑ready?
No, the SDK is currently a work in progress and explicitly labeled as not ready for production use.
@jgmartin
基本情報
An MCP client/server library for Rust
ツール一覧はまだありません
この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。
ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。
A Rust implementation of the Model Context Protocol (MCP), designed for seamless communication between AI models and their runtime environments. It is currently a work in progress and not ready for production use.
Add mcp_sdk_rs = "0.1.0" to your Cargo.toml. Then use the provided client and server examples: create a transport (WebSocket or stdio), set up mpsc channels, start a session, and make requests or serve. Both examples use Tokio for async execution.
No, the SDK is currently a work in progress and explicitly labeled as not ready for production use.
It supports WebSocket (secure and standard) for network communication and stdio for local process communication.
The SDK uses Tokio for async runtime and provides async/await support throughout.
The SDK provides a comprehensive `Error` type that distinguishes protocol errors, transport errors, and other errors, enabling fine‑grained error handling.
The project is licensed under the MIT License. It was originally forked from [mcp-rust-sdk](https://github.com/Derek-X-Wang/mcp-rust-sdk).

ArtiBot Cloud MCP (Zhijiangyun 智匠云) — cloud MCP server for robot manipulation data & GPU workloads. 15 tools: robot fleet management, data collection & video recording, post-processing pipelines, and benchmark evaluation

SSH MCP server for AI agents: remote commands, file transfer, log search and server audits through OpenSSH.

Launch your product from your AI agent. Connect Claude Code, Codex, Cursor or ChatGPT to Launchdog over MCP and your agent drafts the listing, picks a launch week and books it. 50 launches a week, ranked only by human vo
MeroFoundry is a remote MCP server available at https://platform.merofoundry.com/mcp.

Routebase keeps your API's design, docs, contract tests, mocks and monitoring in one living OpenAPI spec so they can't drift apart. Agents work on that same source of truth, under your team's permissions.
コメント