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. This Skill provides the patterns and guidance to implement MCP servers in Node/TypeScript without guessing at current API signatures. ## Core Features & Use Cases - Tool, Resource, and Prompt Registration: Register callable tools with Zod-validated input schemas, read-only resources with URI handlers, and parameterized prompt templates using the @modelcontextprotocol/sdk. - Transport Selection Guidance: Choose stdio for local clients like Claude Desktop or Streamable HTTP for remote clients like Cursor, with notes on legacy HTTP/SSE backward compatibility. - SDK Version Awareness: Directs verification against Context7 or official MCP docs since registration APIs (tool() vs registerTool()) change across SDK versions. - Use Case: You need to expose an internal search API to Claude Desktop. Use this Skill to scaffold an MCP server, register a search tool with a Zod schema, and connect it over stdio. ## Quick Start Use the mcp-server-patterns skill to scaffold an MCP server in TypeScript with one Zod-validated tool and a stdio transport.