mcp-server-implementlisted

Build an MCP server in Rust — tool attributes, server lifecycle (initialize → capabilities → shutdown), transport choice (stdio vs Streamable HTTP), stderr-only logging, error mapping, and testing with the MCP Inspector in CLI mode (no browser). Use when the user says "implement an MCP server in Rust", "build an MCP tool", "Rust MCP server", "transport choice stdio vs HTTP", "MCP server lifecycle".
Git-Fg/taches-principled · ★ 0 · AI & Automation · score 73

Install: claude install-skill Git-Fg/taches-principled

# mcp-server-implement The production side: build an MCP server in Rust with `rmcp` + `schemars`. For the design principles (when to split tools, output contract, error codes), see `mcp-server-design`. For the JSON Schema authoring details, see `mcp-tool-surface`. ## §1. When this skill fires **Use this skill when the user says any of:** - "Implement an MCP server in Rust" - "Use rmcp + schemars" - "Build an MCP tool in Rust" - "Add a tool to my existing MCP server" - "Set up an MCP server with stdio / Streamable HTTP" - "How do I declare capabilities in rmcp?" - "Map Rust types to JSON Schema for MCP" - "Implement an MCP tool with structured output" ## CONTRAST - NOT for: designing an MCP server's tool decomposition or output contract — use mcp-server-design - NOT for: writing the JSON Schema for a single tool — use mcp-tool-surface - NOT for: MCP server implementation in Python / TypeScript / Go — use the SDK-specific docs - This skill covers Rust implementation (rmcp + schemars + tokio) only; the design and schema layers are separate skills - "Build an MCP client" → not covered (no client skill yet) ## §2. Reference index The mechanism content lives in references/. Read the right one before implementing the corresponding phase. The hub itself is a router — it tells you which reference to load, not how to implement. You MUST read `references/rmcp-api.md` BEFORE writing the `Cargo.toml`, the server struct, or any `#[tool]`-annotated methods. It teaches the rmcp 0.3 f