What problem does it solve? Teams generating MCP servers from a codebase risk shipping servers that break against every shipping client, lose safety-critical metadata (read_only, egress, idempotence) that JSON Schema has no slot for, and wrongly assume MCP provides progressive disclosure, tool search, or code-mode execution. ## Core Features & Use Cases - Architecture decision guidance: Keeps a typed internal IR as the single source of truth and projects MCP as an export adapter, never as the internal calling convention. - Protocol churn planning: Covers the four breaking MCP revisions (2024-11-05 through 2026-07-28) and mandates dual-era generated servers that serve legacy initialize and modern per-request _meta on one endpoint. - Emission checklist: Provides a concrete checklist for generated servers covering MRTR input_required gating, handle-passing for cross-call state, deterministic tools/list ordering, and JSON Schema 2020-12 input schemas. - Use Case: When designing an MCP server that exposes a generated tool catalog to Claude, ChatGPT, Cursor, and Gemini, use this Skill to decide the wire revision, transport, and catalog size before writing any server code. ## Quick Start Ask the agent to design the MCP export surface for your generated tool catalog and verify the emitted server against the dual-era compatibility checklist.