What problem does it solve? Building an MCP server involves early decisions — deployment model, tool-design pattern, framework, and auth — that are painful to reverse later. This Skill replaces guesswork with a structured discovery process that interrogates your use case and recommends the right architecture before any code is written. ## Core Features & Use Cases - Use-case interrogation: Asks targeted questions about what the server connects to, who uses it, how many actions it exposes, and what auth the upstream service requires. - Deployment model recommendation: Chooses between remote streamable-HTTP, MCP apps with UI widgets, MCPB bundled local servers, or local stdio prototypes, with opinionated reasoning. - Tool-design patterns: Applies one-tool-per-action for small API surfaces or the search-plus-execute pattern for large APIs with dozens of endpoints. - Scaffolding and handoff: Scaffolds TypeScript SDK or FastMCP servers inline, or hands off to specialized skills for MCP apps and MCPB packaging. - Use Case: You want to wrap your company's SaaS API so Claude users can query it. The Skill determines you need a remote HTTP server with OAuth via CIMD, recommends the search-plus-execute pattern for your 60 endpoints, and scaffolds a Cloudflare Workers deployment. ## Quick Start Ask Claude to help you build an MCP server that wraps your API, and answer its questions about your use case, users, and authentication requirements.
