mcp-server-patterns

Provide reusable patterns for tools, resources, prompts, and transport in Node/TypeScript MCP servers.

1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/sbalagan22/bloomr --skill mcp-server-patterns-sbalagan22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-server-patterns
Source: https://github.com/sbalagan22/bloomr/tree/main/.claude/skills/mcp-server-patterns
Command: npx skills add https://github.com/sbalagan22/bloomr --skill mcp-server-patterns-sbalagan22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build and maintain MCP servers by providing reusable patterns for tools, resources, prompts, and transport configurations, helping teams stay aligned as the MCP SDK evolves.

Core Features & Use Cases

  • Core concepts: Tools, Resources, Prompts, and Transport; guidance for registering and wiring these components across different SDK versions.
  • Transport options: stdio for local development and Streamable HTTP for remote clients, with best practices for switching transports.
  • Practical scenarios: onboarding new MCP servers, adding tools/resources, debugging registrations, and upgrading SDKs.
  • Official docs: references to Context7 MCP docs and SDKs for JavaScript/TypeScript, Go, and C#.

Quick Start

Create a minimal MCP server skeleton that registers a tool and a resource, then run it locally using stdio transport.

Frequently Asked Questions about mcp-server-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a Node TypeScript MCP server with tools and resources?

Structure a Node TypeScript MCP server by using reusable patterns to register tools and resources, wiring them through the provided SDK registration APIs. This approach ensures your components are correctly configured across multiple SDK versions.

When should I use stdio vs Streamable HTTP transport for an MCP server?

Use stdio transport for local MCP server development and Streamable HTTP transport for remote clients. Switching between these transport configurations follows specific best practices outlined in the server patterns to match your deployment target.

How do I validate MCP tool arguments in a TypeScript SDK?

Validate MCP tool arguments in TypeScript by applying schema validation with libraries like Zod during the tool registration process. This ensures input conformity before the tool executes the requested operations.

Can I use these MCP server patterns across different SDK versions?

Yes, these MCP server patterns apply to Node TypeScript servers across multiple SDK versions. They provide specific guidance for wiring tools, resources, and prompts to help teams stay aligned as the SDK evolves.

What is the best way to add new tools and resources to an existing MCP server?

The best way to add tools and resources to an MCP server is by following the reusable pattern-driven registration APIs. This standardizes component integration and simplifies debugging registrations during onboarding or upgrades.

Why do my MCP server registrations fail after an SDK upgrade?

MCP server registrations often fail after an SDK upgrade due to changes in registration APIs across versions. Applying the version-specific pattern guidance for tools and resources resolves these compatibility issues.