mcp-builder

# MCP builder ## Contract | Field | Bound contract | |---|---| | Trigger | Creating an MCP server to integrate an API or service in Python or TypeScript. | | Authority | Reversible local: writes only named project files; rollback is deleting the project directory. No remote mutation. | | Side effect | A new MCP server project with typed tools, tests, and a read-only evaluation suite. | | Done | Server builds, registers tools with correct Zod/Pydantic schemas and annotations, passes MCP inspector, and has 16 stable read-only evaluations with verified answers. | ## Inputs - API or service specification (required): endpoint list, auth method, request/response shapes, or OpenAPI/GraphQL schema describing the service to integrate. - Language (required): `python` or `typescript`. - Project directory (required): target path for the new MCP server project. - Tool design intent (optional): which operations to expose as MCP tools and any annotation hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint). ## Procedure 1. Validate inputs: confirm the API specification is parseable, the language is `python` or `typescript`, and the project directory does not already exist or is empty. Done when: all three validations pass or the run stops with the specific failure. 2. Scaffold the project. TypeScript: initialize with `pnpm init`, then run `pnpm add @modelcontextprotocol/sdk zod`; create `src/index.ts` as the server entry point. Python: initialize with `uv init`, install...