Mcp Server Patterns

Covers the practical patterns for building MCP servers with the Node/TypeScript SDK: registering tools, resources, and prompts, choosing between stdio for local clients like Claude Desktop and Streamable HTTP for remote ones, and handling Zod validation. The guide is honest about API churn in the SDK, repeatedly nudging you to check Context7 or the official docs for current method signatures rather than blindly copying examples. Use this when you're spinning up a new MCP server or debugging why your tools aren't showing up. The schema-first approach and separation of server logic from transport are solid architectural advice that will save you refactoring pain later.

skills.sh installs: 5.6K
GitHub stars: 300.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/ecc --skill mcp-server-patterns --agent claude-code

Installs into .claude/skills of the current project.

Files

MCP Server Patterns

The Model Context Protocol (MCP) lets AI assistants call tools, read resources, and use prompts from your server. Use this skill when building or maintaining MCP servers. The SDK API evolves; check Context7 (query-docs for "MCP") or the official MCP documentation for current method names and signatures.

For the broader routing decision of when a capability should be a rule, a skill, MCP, or a plain CLI/API workflow, see docs/capability-surface-selection.md.

When to Use

Use when: implementing a new MCP server, adding tools or resources, choosing stdio vs HTTP, upgrading the SDK, or debugging MCP registration and transport issues.