Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
jeffallan avatar

Mcp Developer

  • 3k installs
  • 10.8k repo stars
  • Updated May 20, 2026
  • jeffallan/claude-skills

mcp-developer is an agent skill that scaffolds, implements, tests, and deploys MCP servers and clients with validated tools, resources, and stdio, HTTP, or SSE transports.

About

mcp-developer is an agent skill for Model Context Protocol server and client implementation in TypeScript or Python. The workflow covers requirement analysis, project scaffolding with create-server or pip install mcp, protocol design for resource URIs and tool schemas, handler implementation, interactive testing with the MCP inspector, and deployment with auth and rate limiting. Reference files cover JSON-RPC 2.0 protocol rules, TypeScript and Python SDK usage, tool definitions, and resource providers. Minimal examples register Zod or Pydantic validated tools such as get_weather and config resources over stdio transport. Constraints require correct JSON-RPC 2.0 behavior, schema validation on every tool input, proper transport selection, structured error responses, authentication, logging, and rate limiting before production. Developers reach for it when scaffolding MCP integrations, debugging protocol compliance, or extending tool and resource handlers for AI clients.

  • Six-step workflow from requirements through scaffold, protocol design, implementation, inspector testing, and deploy.
  • Includes TypeScript McpServer and Python FastMCP examples with Zod or Pydantic validated tool inputs.
  • Reference map covers protocol, TypeScript SDK, Python SDK, tools, and resources documentation files.
  • Mandates JSON-RPC 2.0 compliance, schema validation, structured errors, auth, logging, and rate limiting.
  • Recommends npx @modelcontextprotocol/inspector for interactive protocol compliance verification.

Mcp Developer by the numbers

  • 3,049 all-time installs (skills.sh)
  • +87 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #246 of 16,659 AI & Agent Building skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

mcp-developer capabilities & compatibility

Capabilities
mcp server scaffolding · tool schema validation · resource provider design · transport configuration · protocol compliance testing
Works with
openai · anthropic
Use cases
api development · orchestration
From the docs

What mcp-developer says it does

Implement JSON-RPC 2.0 protocol correctly
SKILL.md
Validate all inputs with schemas (Zod/Pydantic)
SKILL.md
npx skills add https://github.com/jeffallan/claude-skills --skill mcp-developer

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs3k
repo stars10.8k
Security audit2 / 3 scanners passed
Last updatedMay 20, 2026
Repositoryjeffallan/claude-skills

How do I build or debug an MCP server with correct JSON-RPC tools, resources, schemas, and transport configuration?

Build, debug, and extend MCP servers and clients with validated tool schemas, resources, and stdio, HTTP, or SSE transport layers.

Who is it for?

Developers implementing MCP integrations in TypeScript or Python who need protocol-correct tools, resources, and transport setup.

Skip if: Skip when the task is generic REST API work without MCP protocol requirements or client-server JSON-RPC semantics.

When should I use this skill?

User builds, debugs, or extends MCP servers or clients, tool handlers, resource providers, or transport layers.

What you get

Working MCP server or client code with validated tool schemas, resource handlers, inspector-tested protocol compliance, and deployment guidance.

  • MCP server implementation
  • Tool and resource handler definitions

By the numbers

  • Built on JSON-RPC 2.0 message format for MCP client-server communication

Files

SKILL.mdMarkdownGitHub ↗

MCP Developer

Senior MCP (Model Context Protocol) developer with deep expertise in building servers and clients that connect AI systems with external tools and data sources.

Core Workflow

1. Analyze requirements — Identify data sources, tools needed, and client apps 2. Initialize projectnpx @modelcontextprotocol/create-server my-server (TypeScript) or pip install mcp + scaffold (Python) 3. Design protocol — Define resource URIs, tool schemas (Zod/Pydantic), and prompt templates 4. Implement — Register tools and resource handlers; configure transport (stdio/SSE/HTTP) 5. Test — Run npx @modelcontextprotocol/inspector to verify protocol compliance interactively; confirm tools appear, schemas accept valid inputs, and error responses are well-formed JSON-RPC 2.0. Feedback loop: if schema validation fails → inspect Zod/Pydantic error output → fix schema definition → re-run inspector. If a tool call returns a malformed response → check transport serialisation → fix handler → re-test. 6. Deploy — Package, add auth/rate-limiting, configure env vars, monitor

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
Protocolreferences/protocol.mdMessage types, lifecycle, JSON-RPC 2.0
TypeScript SDKreferences/typescript-sdk.mdBuilding servers/clients in Node.js
Python SDKreferences/python-sdk.mdBuilding servers/clients in Python
Toolsreferences/tools.mdTool definitions, schemas, execution
Resourcesreferences/resources.mdResource providers, URIs, templates

Minimal Working Example

TypeScript — Tool with Zod Validation

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

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

// Register a tool with validated input schema
server.tool(
  "get_weather",
  "Fetch current weather for a location",
  {
    location: z.string().min(1).describe("City name or coordinates"),
    units: z.enum(["celsius", "fahrenheit"]).default("celsius"),
  },
  async ({ location, units }) => {
    // Implementation: call external API, transform response
    const data = await fetchWeather(location, units); // your fetch logic
    return {
      content: [{ type: "text", text: JSON.stringify(data) }],
    };
  }
);

// Register a resource provider
server.resource(
  "config://app",
  "Application configuration",
  async (uri) => ({
    contents: [{ uri: uri.href, text: JSON.stringify(getConfig()), mimeType: "application/json" }],
  })
);

const transport = new StdioServerTransport();
await server.connect(transport);

Python — Tool with Pydantic Validation

from mcp.server.fastmcp import FastMCP
from pydantic import BaseModel, Field

mcp = FastMCP("my-server")

class WeatherInput(BaseModel):
    location: str = Field(..., min_length=1, description="City name or coordinates")
    units: str = Field("celsius", pattern="^(celsius|fahrenheit)$")

@mcp.tool()
async def get_weather(location: str, units: str = "celsius") -> str:
    """Fetch current weather for a location."""
    data = await fetch_weather(location, units)  # your fetch logic
    return str(data)

@mcp.resource("config://app")
async def app_config() -> str:
    """Expose application configuration as a resource."""
    return json.dumps(get_config())

if __name__ == "__main__":
    mcp.run()  # defaults to stdio transport

Expected tool call flow:

Client → { "method": "tools/call", "params": { "name": "get_weather", "arguments": { "location": "Berlin" } } }
Server → { "result": { "content": [{ "type": "text", "text": "{\"temp\": 18, \"units\": \"celsius\"}" }] } }

Constraints

MUST DO

  • Implement JSON-RPC 2.0 protocol correctly
  • Validate all inputs with schemas (Zod/Pydantic)
  • Use proper transport mechanisms (stdio/HTTP/SSE)
  • Implement comprehensive error handling
  • Add authentication and authorization
  • Log protocol messages for debugging
  • Test protocol compliance thoroughly
  • Document server capabilities

MUST NOT DO

  • Skip input validation on tool inputs
  • Expose sensitive data in resource content
  • Ignore protocol version compatibility
  • Mix synchronous code with async transports
  • Hardcode credentials or secrets
  • Return unstructured errors to clients
  • Deploy without rate limiting
  • Skip security controls

Output Templates

When implementing MCP features, provide: 1. Server/client implementation file 2. Schema definitions (tools, resources, prompts) 3. Configuration file (transport, auth, etc.) 4. Brief explanation of design decisions

Documentation

Related skills

How it compares

Pick mcp-developer over generic API-building skills when the target is MCP-specific JSON-RPC tooling rather than REST or GraphQL endpoints.

FAQ

How do I scaffold a new MCP server?

Use npx @modelcontextprotocol/create-server for TypeScript or pip install mcp with a Python scaffold before registering tools.

How should tool inputs be validated?

Validate all tool inputs with Zod in TypeScript or Pydantic in Python before executing handlers.

How do I verify MCP protocol compliance?

Run npx @modelcontextprotocol/inspector to confirm tools appear, schemas accept valid inputs, and errors are well-formed JSON-RPC 2.0.

Is Mcp Developer safe to install?

skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

AI & Agent Buildingagentsautomation

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.