MCP Builder
Build MCP servers around user workflows, not raw API endpoints.
Workflow
- Read the target API docs and identify the workflows an agent must complete end to end.
- Design a small tool surface with high-signal outputs, clear identifiers, and actionable errors.
- Implement shared infrastructure first: auth, request helpers, pagination, truncation, and formatting.
- Add tool schemas and docstrings that make correct usage obvious.
- Evaluate the server with realistic tasks before expanding scope.
Principles
- Prefer workflow tools over thin endpoint wrappers.
- Return concise, high-signal responses by default.
- Use human-readable identifiers whenever possible.
- Make error messages corrective: tell the agent what to try next.
- Design for limited context and large datasets.
Resources
references/mcp_best_practices.mdfor design principles that apply to every server.references/python_mcp_server.mdfor Python implementation patterns.references/node_mcp_server.mdfor TypeScript implementation patterns.scripts/connections.pyandscripts/evaluation.pyas repo-local helpers.
Deliverables
- A concrete tool inventory tied to user workflows.
- Strict input/output schemas.
- Evaluation prompts or scripts that confirm the server is usable by an agent.