mcp-builder

# MCP Server Development Adapted from [anthropics/skills/mcp-builder](https://github.com/anthropics/skills/tree/main/skills/mcp-builder). MCP-server quality is measured by how well it lets LLMs accomplish real-world tasks — not by endpoint count. ## Stack default for our projects - **Language:** TypeScript (matches our stack; static typing + Zod schemas + good LLM code-gen) - **Transport:** `stdio` for local tools, **Streamable HTTP (stateless JSON)** for remote - **SDK:** [`@modelcontextprotocol/sdk`](https://github.com/modelcontextprotocol/typescript-sdk) - **Package manager:** pnpm (never npm/yarn in our repos) ## Phase 1 — Research & Plan ### 1.1 Design principles **API coverage vs. workflow tools.** Balance comprehensive endpoint coverage with specialized workflow shortcuts. Default to coverage unless you have a clear reason — agents compose basic tools well; workflow tools ossify. **Tool naming & discoverability.** Consistent prefix + action verb. Examples: - `github_create_issue`, `github_list_repos` - `gitlab_search_issues`, `gitlab_close_mr` **Context management.** Return focused, paginated data. Agents suffer when a single tool call floods context. **Actionable error messages.** Errors must guide the next action: ``` ❌ "Invalid input" ✅ "Field 'project_id' is required. Call gitlab_list_projects to enumerate available IDs." ``` ### 1.2 Read the spec - Sitemap: `https://modelcontextprotocol.io/sitemap.xml` - Append `.md` to any page URL for markdown (e.g. ...