What problem does it solve? Building an MCP server involves version-sensitive protocol rules, SDK divergences, and security pitfalls that silently break clients: tools the model never picks, truncated results, corrupted stdio streams, and misconfigured OAuth. This Skill encodes the measured, revision-gated rules for the 2026-07-28 specification so a server works correctly the first time. ## Core Features & Use Cases - Server design and implementation: Decide primitives (tools vs resources vs prompts), write tool descriptions and schemas the model can act on, budget result sizes, and construct recoverable errors. - Transport and protocol compliance: Configure stdio framing and Streamable HTTP with the required headers, handle the modern/legacy era split, and migrate across specification revisions. - Security review and publishing: Audit authorization (audience validation, no token passthrough, scope minimization), defend against tool poisoning and command injection, and verify the published install config with the Inspector CLI. - Use Case: Given an existing TypeScript MCP server where agents pick the wrong tool and the process randomly hangs, the Skill identifies stdout logging as the protocol-framing bug, splits a multiplexed op-dispatch tool, and produces fixed tool definitions. ## Quick Start Ask the agent to review your MCP server file and fix its tool definitions, transport setup, and authorization configuration against the 2026-07-28 specification.