MCP Server Sprint, fixed price, 7 days

Put Your Product Inside Claude, Cursor and VS Code

I build an MCP server on the API you already have. Seven days, $990 for the first five clients, then $1,490.

$990First five clients, then $1,490
7 daysFixed time
8 toolsUp to
24 hoursFit confirmed or refunded

Pay, send your docs and a test key, and within 24 hours I confirm the tool list or refund you. By day 7 you get the repo, the package, the docs and a recording of your five prompts working, or your money back.

The plan

How the Seven Days Go

  1. Day 0

    Pay, then send your docs

    Checkout takes you to the intake: your docs link, how your API authenticates, the clients your users work in, and the five prompts that must work. I ask for a test key by reply, never in a form.

  2. Within 24 hours

    The tool list, or your money back

    I read your docs and confirm the tools I will build, up to 8. If your API is not a fit, you get a full refund and nothing else is asked of you.

  3. Days 2 to 6

    The build

    The server, its tests and its install docs, on the API and the keys you already have. You see progress as it lands, not a status meeting.

  4. Day 7

    Delivered, or refunded

    You get the repo, the package, the docs and a recording of your five prompts working. If the agreed prompts fail, you get your money back.

In the box

What You Get

  • Up to 8 tools on your existing API, chosen from your docs and your five prompts.
  • An npm package, plus a remote endpoint that uses your existing API keys.
  • Tests for every tool, and install docs for Claude, Cursor and VS Code.
  • A listing in the official MCP Registry, so clients can find it.
  • 14 days of fixes after delivery.

Money back, twice

The Guarantee

Two points where you can walk away with your money. Within 24 hours of payment I confirm the fit and the tool list, or refund you. By day 7, if the five prompts we agreed on do not work, you get a full refund.

What It Does Not Cover

OAuth is quoted separately. The sprint builds on the API and the keys you already run; if your users need to sign in with OAuth, I quote that part once I have seen your auth. If an endpoint your prompts need does not exist yet, I tell you in the first 24 hours rather than build around it.

Why Me

I built toolindex.net/api/mcp, the MCP server that lets Claude search Tool Index, and I published Apatero Studio's server on npm as apatero-mcp and on PyPI as apatero-studio-mcp. You talk to the person writing the code, start to finish.

Straight answers

Questions

What is an MCP server?

A small server that speaks the Model Context Protocol, the standard Claude, Cursor and VS Code use to call tools. Once it wraps your API, your users can ask their assistant to do things in your product in plain language.

What do you need from me?

Your docs link, a test API key, the clients your users work in, and the five prompts that must work by day 7. The intake takes everything except the key, which I ask for by reply.

What if my API is not a fit?

Within 24 hours of your payment I either confirm the tool list or refund you in full.

What if the prompts do not work?

If the five prompts we agreed on do not work by day 7, you get a full refund.

Do you support OAuth?

The sprint uses your existing API keys. If your users need to sign in with OAuth, I quote that part separately once I have seen your auth.

Why $990?

It is the launch price for the first five clients. After that the sprint is $1,490.

What happens after day 7?

14 days of fixes. After that you have the repository, the package and the docs to run it yourself.

Ready When Your Docs Are

Not ready to pay? Send your docs first and I will reply with the 8 tools I would build first, free.