Build
An MCP server for your API or website, built, hosted and submitted.
$4,900 one-time · 50% deposit to start, balance on delivery
10 business days
A user opens Claude or ChatGPT, asks a question about your product, and gets an answer from your data, with your name on the tool that produced it. That is what an MCP server does for you, and it is what the Build delivers: the server, the hosting, the monitoring, and everything the directories need to list it.
Eight tools is deliberate. A server with forty tools is worse for the model and worse for the review; the kickoff call is where we decide which eight questions a user would actually ask, and those become the tools. Read tools first, because the directories accept them most easily and most products need nothing else to be useful in a chat.
What is included
- Up to 8 tools from your REST, GraphQL or OpenAPI, or a read layer over your website
- Streamable HTTP transport on the current protocol version
- OAuth 2.0 with dynamic client registration where the directory requires it
- Staging URL and MCP Inspector access while we build
- Uptime and tools/list drift monitoring for the first 30 days
- The full Listing Sprint on top, so it goes into review the day it is done
- Code handed over in a repository you own
What we need from you
- API documentation, an OpenAPI file, or a walkthrough of what the product does
- A test account with realistic data, and API credentials for it
- Someone who answers questions within a business day
- The Owner of your Claude or OpenAI organisation, for thirty minutes at the end
Not included
- Changes to your own API
- Consumer-facing apps (the directories list business tools)
Timeline
What happens when.
| Day 1 | Kickoff: the eight tools, the auth flow, where it will be hosted. Written scope the same day. |
|---|---|
| Days 2 to 5 | Server on a staging URL. You add it to Claude as a custom connector and try it. Inspector access for every tool. |
| Days 6 to 8 | OAuth, error handling, rate limits, descriptions tuned against real prompts. Monitoring switched on. |
| Days 9 to 10 | The Listing Sprint: documents, assets, test account, submission together. Repository handed over. |
Questions
Specific to this package.
Can the server write data, not just read it?
Yes. Write tools carry a destructiveHint, a confirmation step where the directories want one, and the OAuth scopes to match. We usually ship reads first and add writes in the same package once the read tools are through review, so a write-side question never blocks the listing.
We already have an OpenAPI file. Is that not enough on its own?
Generators exist and we use them for the first pass. What they do not do is choose the eight tools, write descriptions a model picks correctly, handle the auth modes the directories require, or get you through review. That is the part you are paying for.
Why a deposit?
Half at the start, half on delivery. The deposit books the ten days in our calendar; the balance is invoiced when the server is on staging and submitted. If we cannot deliver what the written scope says, the deposit comes back.
The general questions, who submits, who owns the code, where it is hosted, are answered on the home page.
Build, $4,900 one-time.
Not this one? Listing Sprint, $1,900 or Care, $390.