mcp-builder

Use the MCP TypeScript SDK's McpServer class and register tools with server.registerTool, providing a title, description, Zod inputSchema, and annotations. Build with tsc and test using the MCP Inspector via npx @modelcontextprotocol/inspector.

Create an XML file with qa_pair elements containing questions and verifiable answers, then run scripts/evaluation.py with your transport type. The harness connects via stdio, SSE, or HTTP and reports accuracy, tool calls, and agent feedback.

Use stdio for local integrations and command-line tools where the server runs as a subprocess. Use streamable HTTP for remote servers serving multiple clients, and avoid SSE since it is deprecated in favor of streamable HTTP.

Use snake_case names with a service prefix like github_create_issue, provide concise descriptions, validate inputs with Zod or Pydantic, support pagination with limit and offset, and return actionable error messages. Add annotations such as readOnlyHint and destructiveHint.

Questions must be independent, read-only, complex enough to require multiple tool calls, realistic, and have a single stable answer verifiable by string comparison. Avoid questions whose answers change over time, such as counts of current open items.