What problem does it solve? Building a Model Context Protocol server requires navigating an evolving SDK API, choosing between stdio and Streamable HTTP transports, and correctly registering tools, resources, and prompts—mistakes here cause registration and connection failures that are hard to debug. ## Core Features & Use Cases - Server scaffolding guidance: Set up an MCP server with @modelcontextprotocol/sdk and Zod, with schema-first input validation for every tool. - Transport selection: Choose stdio for local clients like Claude Desktop or Streamable HTTP for remote clients like Cursor, keeping server logic transport-independent. - Registration patterns: Register tools, resources, and prompts correctly across SDK versions (tool() vs registerTool()), verifying signatures against official docs or Context7. - Use Case: You are adding a new search tool to an internal MCP server used by Claude Desktop. Use this Skill to define the Zod input schema, register the tool with the correct SDK method, and connect over stdio. ## Quick Start Use the mcp-server-patterns skill to scaffold a new MCP server in TypeScript with one Zod-validated tool and a stdio transport.