mcp-builder

Use the MCP TypeScript SDK's McpServer class and registerTool method with Zod schemas for input validation. Provide title, description, inputSchema, and annotations for each tool, then connect via StdioServerTransport for local use or StreamableHTTPServerTransport for remote deployment.

Create an XML file with qa_pair elements containing questions and verifiable answers, then run the evaluation.py script with your transport type. For stdio servers the script launches the server automatically; for SSE or HTTP you must start the server first and pass its URL.

Use stdio for local integrations and command-line tools with a single client, and streamable HTTP for remote servers serving multiple clients. SSE is deprecated in favor of streamable HTTP, and stdio servers must log to stderr rather than stdout.

Use snake_case with a service prefix and action-oriented verbs, such as github_create_issue or slack_send_message. This prevents naming conflicts when multiple MCP servers are used together and helps agents discover the right tool quickly.

Questions must be independent, read-only, non-destructive, and complex enough to require multiple tool calls. Answers must be single verifiable values that remain stable over time and can be checked by direct string comparison.