claudegoodies
Skill

mcp-server-patterns

From affaan-m

Build MCP servers with Node/TypeScript SDK — tools, resources, prompts, Zod validation, stdio vs Streamable HTTP. Use Context7 or official MCP docs for latest API.

Guides building MCP servers in Node/TypeScript covering tools, resources, prompts, and transport choice.

Use it when

  • Implementing a new MCP server from scratch
  • Adding tools, resources, or prompts to an existing server
  • Deciding between stdio and Streamable HTTP transport
  • Upgrading the @modelcontextprotocol/sdk and hitting API changes

Skip it if

  • You need exact current SDK method signatures, not just concepts (it tells you to check Context7/docs instead)
  • You're not using Node/TypeScript (Go and C# SDKs only mentioned by name)
  • You want a ready-made server, not pattern guidance

Facts

Repository
affaan-m/ECC
Status
Actively maintained
Last commit
Source file
.agents/skills/mcp-server-patterns/SKILL.md

Source preview

The instructions Claude Code reads when this skill runs.

# 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.

## 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.

## How It Works

### Core concepts

- **Tools**: Actions the model can invoke (e.g. search, run a command). Register with `registerTool()` or `tool()` depending on SDK version.
- **Resources**: Read-only data the model can fetch (e.g. file contents, API responses). Register with `registerResource()` or `resource()`. Handlers typically receive a `uri` argument.
- **Prompts**: Reusable, parameterised prompt templates the client can surface (e.g. in Claude Desktop). Register with `registerPrompt()` or equivalent.
- **Transport**: stdio for local clients (e.g. Claude Desktop); Streamable HTTP is preferred for remote (Cursor, cloud). Legacy HTTP/SSE is for backward compatibility.

The Node/TypeScript SDK may expose `tool()` / `resource()` or `registerTool()` / `registerResource()`; the official SDK has changed over time. Always verify against the current [MCP docs](https://modelconte
View full source on GitHub →

Other skills