mcp-builderlisted

# MCP Server Development Guide # Process ## Contract Inputs: - Requested integration, target repository, API documentation, and approved service scope Outputs: - MCP server implementation, tool contracts, and scoped verification evidence Creates/Modifies: - Source, tests, and evaluation fixtures required for the requested server External Side Effects: - Documentation reads; provider calls and paid evaluations only when authorized Confirmation Required: - Before credentialed service writes, paid evaluation runs, publishing, or configuring an agent outside the requested scope - Loading the skill grants no additional authority. Existing explicit approval applies only to the same target and actions; preserve report-only restrictions. Delegates To: - None ## High-Level Workflow Build an MCP server in four phases: ### Phase 1: Deep Research and Planning #### 1.1 Understand Agent-Centric Design Principles Before implementation, design tools around agent workflows: **Build for Workflows, Not Just API Endpoints:** - Do not mirror every API endpoint by default. Group endpoints into workflow tools when one user task requires multiple API calls. - Consolidate related operations (e.g., `schedule_event` that both checks availability and creates event) - List the top user workflows and map each tool to one workflow. **Optimize for Limited Context:** - Return only fields needed for the task by default. - Return high-signal information, not exhaustive data dumps - P