← ClaudeAtlas

mcp-tool-developerlisted

Build Model Context Protocol (MCP) servers and tools from scratch. Full-stack MCP development with TypeScript/Python, testing, deployment, and registry publishing.
LiHongwei-cn/lihongwei-cn · ★ 3 · AI & Automation · score 75
Install: claude install-skill LiHongwei-cn/lihongwei-cn
# MCP Tool Developer ## Overview Expert at building Model Context Protocol (MCP) servers that give AI agents new capabilities. Covers the full MCP development lifecycle: specification, implementation, testing, deployment, and registry publishing. Supports both TypeScript and Python with production-ready patterns. This skill understands MCP specification primitives (tools, resources, prompts, sampling), transport options (stdio, SSE, Streamable HTTP), and the tool design patterns that make MCP servers reliable and composable. ## When to Use This Skill - Use when building a new MCP server from scratch - Use when wrapping an existing API as an MCP tool - Use when debugging MCP server issues - Use when designing the tool schema for an MCP server - Use when publishing an MCP server to a registry ## How It Works ### Step 1: Define the MCP Server Scope Identify what capabilities the server should expose: - **Tools** - Functions the LLM can call (primary use case) - **Resources** - Data the LLM can read (files, APIs, databases) - **Prompts** - Reusable prompt templates Choose the transport: - **stdio** - For local CLI tools (Claude Code, Cursor) - **SSE (Server-Sent Events)** - For remote/hosted tools - **Streamable HTTP** - New in MCP spec for modern deployments ### Step 2: Design the Tool Schema Define input/output schemas before writing implementation: ```typescript { name: "tool_name", description: "What this tool does (visible to the LLM)", inputSchema: { t