Plan and build an MCP server that connects AI to my service
A tool design and starter code for a Model Context Protocol server that lets AI assistants use your API well.
The prompt
Help me design and build an MCP (Model Context Protocol) server so AI assistants can use my service.
Service or API: [NAME and what it does]
API documentation: [paste endpoints, auth method, rate limits, pagination]
What users will ask the AI to do: [3-5 real tasks, e.g. "find overdue invoices for a customer and draft a reminder"]
Language/SDK: [Python (FastMCP) / TypeScript (official MCP SDK)]
Transport: [local stdio / remote HTTP]
Read-only or write actions? [which actions change data]
Step 1: Tool design (before code)
- Design tools around the user tasks, not one tool per endpoint. Combine calls where a task needs several.
- For each tool: name, one-line purpose, input schema with clear parameter descriptions, and what it returns.
- Keep responses concise: return the fields the AI needs, support a short vs. detailed format, and paginate or truncate large results with a clear note.
- Write error messages that tell the AI what to do next (e.g. "No customer found; try search_customers first").
- Mark destructive or write tools clearly and require explicit parameters for them.
Step 2: Code
- A working server skeleton with the tools, input validation, auth read from environment variables (never hard-coded), and rate-limit handling.
Step 3: Test plan
- How to run it with the MCP Inspector, plus 5-10 realistic test questions that require multiple tool calls, with expected results.
Return the tool table first, then the code, then the test plan. Flag any SDK detail you are unsure about as [VERIFY IN SDK DOCS], since the protocol and SDKs change.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Working with AI prompts
What to fill in
- NAME and what it does
- paste endpoints, auth method, rate limits, pagination
- Python (FastMCP) / TypeScript (official MCP SDK)
- local stdio / remote HTTP
- which actions change data
- VERIFY IN SDK DOCS
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Plan what to do when AI gets something wrong at workAn escalation path for AI errors: how to spot, contain, report, fix, and learn from mistakes made with AI tools.
- Choose between a chatbot, copilot, automation, or AI agent for a taskRecommends the right kind of AI setup for a task, with the trade-offs, risks, and what you need to make it work.
- Create a personal AI capability roadmap for my roleA staged plan to grow from occasional AI user to someone who builds and directs AI workflows in your job.
- Turn a rough request into a powerful promptRewrites your idea into a clear, complete prompt — and asks what's missing first.