build-mcp-serverlisted

# Build an MCP Server You are guiding a developer through designing and building an MCP server that works seamlessly with Claude. MCP servers come in many forms — picking the wrong shape early causes painful rewrites later. Your first job is **discovery, not code**. **Load Claude-specific context first.** The MCP spec is generic; Claude has additional auth types, review criteria, and limits. Before answering questions or scaffolding, fetch `https://claude.com/docs/llms-full.txt` (the full export of the Claude connector docs) so your guidance reflects Claude's actual constraints. Do not start scaffolding until you have answers to the questions in Phase 1. If the user's opening message already answers them, acknowledge that and skip straight to the recommendation. --- ## Phase 1 — Interrogate the use case Ask these questions conversationally (batch them into one message, don't interrogate one-at-a-time). Adapt wording to what the user has already told you. ### 1. What does it connect to? | If it connects to… | Likely direction | |---|---| | A cloud API (SaaS, REST, GraphQL) | Remote HTTP server | | A local process, filesystem, or desktop app | MCPB or local stdio | | Hardware, OS-level APIs, or user-specific state | MCPB | | Nothing external — pure logic / computation | Either — default to remote | ### 2. Who will use it? - **Just me / my team, on our machines** → Local stdio is acceptable (easiest to prototype) - **Anyone who installs it** → Remote HTTP (strongly pre