MCP Build · Fixed-price engineering
MCP Server Build
Your users are asking for an MCP server. We build it — fixed price, this month.
Your product has an API, your users have started asking for an MCP server on your issue tracker, and nobody on your team has a free fortnight. That is the whole problem this solves. We build production MCP servers on the current spec revision — Streamable HTTP, OAuth 2.1 where it is needed, schema-validated tools, rate limiting, and an eval suite so you can prove it still works after the next spec change. Fixed price, agreed before we start. A production-grade server built in-house runs $15,000–40,000 of engineering time; we are not competing with free, we are competing with your backlog. Our own reference server is public and running, so you can call the thing we are selling before you buy it.
Built for: Software vendors and open-source maintainers with an API and no MCP server — or a server that predates the current spec
- Built on MCP spec revision 2026-07-28, not a stale tutorial
- Streamable HTTP, remote — not a stdio script your users must install
- A designed tool map: tools an agent can actually use, not one per endpoint
- OAuth 2.1 resource-server auth where the data needs it
- Per-tool rate limiting and structured logging
- An eval suite that calls your tools the way an agent does
- Listed in the official MCP registry and the major catalogs
- Fixed price agreed up front — no hourly, no discovery phase
- $15K–40Kwhat a production server costs to build in-house
- 2026-07-28the spec revision we build to
- 4real bugs our own eval suite caught before launch
- 0calls you have to sit through
What it costs
Registry Launch
$149
You built it. It is not listed anywhere.
- server.json authored and validated
- Submitted to the official MCP registry
- Listed on Glama and two further catalogs
- npm or PyPI publish if you have not published yet
- Smoke-tested from a clean client
- 2 business days
One server published and listed.
Live Tool Preview
$149
See one of your endpoints working before you commit.
- One or two of your endpoints, live as MCP tools
- Running in a real client, screen-recorded
- Streamable HTTP on the current spec
- The full $149 credited toward a Full Build
- 3 business days
One preview for one product; credited toward a build.
MCP Upgrade
$499
You have a server. It predates the current spec.
- stdio to remote (Streamable HTTP)
- Migration to spec 2026-07-28, including SDK v2
- OAuth 2.1 resource-server auth
- Registry listing
- An eval suite, so you can prove it still works
- One week
One existing server migrated.
Full Build · Wrap
$750
You have a documented API. We wrap it properly.
- Up to 12 tools designed around your existing API
- Schema validation, rate limiting, structured logging
- Eval suite + docs
- Registry listing and launch
- 1–2 weeks
One production server for one product.
Full Build · Design
$1,900
The tool map designed from scratch, not mapped off endpoints.
- Everything in Wrap
- Tool map designed from your users' actual jobs
- Auth flows designed with you
- Two rounds of revision on the tool surface
- 1–2 weeks
One production server for one product.
Questions
Can I try your work before paying?
Yes — our own reference server is public and running at mcp.upshiftsites.com/mcp. Point any MCP client at it and call the three tools. It is the same standard of work we ship to clients, including the eval suite and the written-down gaps.
What is an eval suite and why does it matter?
Unit tests check your functions. Evals check what an agent is actually told when it calls your tool — the text, the structured result, the error when it passes something wrong. The MCP spec moves; evals are how you find out a migration broke a tool before your users do. Ours caught four real bugs while we built our own server, including a security one.
Why is 'the spec revision' worth caring about?
Revision 2026-07-28 removed the initialize handshake in favour of a mandatory server/discover call, moved version negotiation into per-request metadata, and dropped session IDs and GET streams. A server written against a 2025 tutorial is not merely dated — modern clients negotiate against it differently. Most of the migration work we are asked for is exactly this.
Do you work on open-source projects?
Yes, and if the project is a well-known one with an open request from its users, ask about a credited contribution instead of an invoice. We do a limited number, and the trade is a public credit.
What if my API is not documented?
Then Wrap is the wrong tier — the Design build exists for that, because the tool map has to come from what your users are trying to do rather than from an endpoint list. If you are not sure which you need, the $149 preview answers it cheaply and comes off the price.
Who owns the code?
You do, outright, in your own repository. No licence, no dependency on us, no hosting lock-in. If you never speak to us again the server keeps running.