What problem does it solve? Deciding whether to build an MCP server, choosing the right transport, and wiring it into Claude Code's mcp.json involves many failure-prone details such as auth token handling, Docker isolation, and tool description quality. This Skill provides decision trees, config patterns, and implementation templates that prevent common mistakes. ## Core Features & Use Cases - Decision Framework: A decision tree for choosing between MCP, Bash, WebFetch, and sub-agents based on auth needs, call frequency, and latency. - Config Patterns: Ready-to-use mcp.json patterns for Docker containers, mcp-remote OAuth services, and local stdio processes with env var injection. - TypeScript Server Template: Guidance for building MCP servers with @modelcontextprotocol/sdk, Zod validation, tool annotations, and pagination. - Evaluation Harness: Python scripts to create and run XML-based evaluations that test whether LLMs can effectively use your MCP server's tools. - Use Case: You need to call an authenticated GitHub-like API repeatedly in a session. Use this Skill to decide MCP is warranted, scaffold a TypeScript server, configure it in mcp.json with Docker isolation, and verify it with claude mcp list. ## Quick Start Ask the agent to help you build and register a new MCP server for an external API in Claude Code, starting with the MCP-versus-Bash decision tree.