|
|
||
|---|---|---|
| .. | ||
| clients | ||
| rig-integration | ||
| servers | ||
| transport | ||
| wasi | ||
| README.md | ||
Quick Start With Claude Desktop
-
Build the Server (Counter Example)
cargo build --release --example servers_std_ioThis builds a standard input/output MCP server binary.
-
Add or update this section in your
~/.config/claude-desktop/config.toml(Linux) or~/Library/Application Support/Claude/claude_desktop_config.json(macOS){ "mcpServers": { "counter": { "command": "PATH-TO/rust-sdk/target/release/examples/servers_std_io.exe", "args": [] } } } -
Ensure that the MCP UI elements appear in Claude Desktop The MCP UI elements will only show up in Claude for Desktop if at least one server is properly configured.
-
Once Claude Desktop is running, try chatting:
counter.say_helloOr test other tools like:
counter.increment counter.get_value counter.sum {"a": 3, "b": 4}
Client Examples
- Client SSE, using reqwest and eventsource-client.
- Client stdio, using tokio to spawn child process.
- Everything, test with
@modelcontextprotocol/server-everything - Collection, How to transpose service into dynamic object, so they will have a same type.
Server Examples
- Server SSE, using axum as web server.
- Server stdio, using tokio async io.
Transport Examples
Integration
- Rig A stream chatbot with rig
WASI
- WASI-P2 runtime How it works with wasip2
Use Mcp Inspector
npx @modelcontextprotocol/inspector