mcp-server-patterns

Compatibility matrix

Platform support, with evidence labels

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Workflow

What the source asks the agent to do

1. 01

   Install and server setup

   Register tools and resources using the API your SDK version provides: some versions use server.tool(name, description, schema, handler) (positional args), others use server.tool({ name, description, inputSchema }, handler) or registerTool(). Same for resources — include a uri in…

   Register tools and resources using the API your SDK version provides: some versions use server.tool(name, description, schema, handler) (positional args), others use server.tool({ name, description, inputSchema }, handl…Use Zod (or the SDK’s preferred schema format) for input validation.
2. 02

   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.

   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.
3. 03

   How It Works

   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 or Context7.

   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.
4. 04

   Core concepts

   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 or Context7.

   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.
5. 05

   Connecting with stdio

   For local clients, create a stdio transport and pass it to your server’s connect method. The exact API varies by SDK version (e.g. constructor vs factory). See the official MCP documentation or query Context7 for "MCP stdio server" for the current pattern.

   For local clients, create a stdio transport and pass it to your server’s connect method. The exact API varies by SDK version (e.g. constructor vs factory). See the official MCP documentation or query Context7 for "MCP s…Keep server logic (tools + resources) independent of transport so you can plug in stdio or HTTP in the entrypoint.

Permission review

Static risk signals and limitations

Pinned source

Provenance and original SKILL.md

Repository

affaan-m/ECC

Skill path

.cursor/skills/mcp-server-patterns/SKILL.md

Commit

4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38

License

MIT

Collected

2026-07-28

Default branch

main

npm install @modelcontextprotocol/sdk zod

import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { z } from "zod";

const server = new McpServer({ name: "my-server", version: "1.0.0" });