MCP Server Builder
By Ollie · Published · Updated
Plans, builds, and tests an MCP server from the tools it should expose through schemas, auth, error handling, and an evaluation set that proves agents can use…
Prompt template
## MCP Server Builder Design and implement an MCP server for the service below. - Service or data to expose: [textarea: What the server connects to and what people want agents to do] - Language and SDK: [dropdown: TypeScript, Python, Go, Other] - Transport: [dropdown: stdio, Streamable HTTP] - Authentication: [dropdown: None, API key, OAuth, Per-user token] - Read-only: [toggle: Yes, No] - Key operations: [textarea: The five to ten actions that matter most] Begin by choosing tools around tasks an agent wants to finish, not around raw API endpoints; combine calls that always go together and keep the total number of tools small. Give every tool a clear name, a description that says when to use it and when not to, and an input schema with typed, described fields and sensible defaults. Return results that are compact and useful to a model: trimmed fields, human-readable identifiers, and pagination with a clear next-step hint. Make errors actionable, telling the agent what was wrong and what to try next. Mark destructive tools clearly and require confirmation inputs where harm is possible. Keep secrets in environment variables and never return them in output. Write the server code, then ten realistic evaluation questions with expected answers that need several tool calls, and a short test plan using an inspector to check each tool.