How to turn your API into an MCP server today?
A remote MCP server turns your API into tools any AI assistant can use, over the internet, not just on your laptop.
APIblaze runs it for you. Point it at your API and you get a live MCP address on Cloudflare’s global network, with sign-in, rules, limits and logs built in. No servers, containers or certificates to manage, it scales on its own, and you pay per request with no subscription.
Put an MCP server online
$ npx apiblaze@latest create --target https://ninopizzas.com/openapi.yamlPaste it in a terminal. No sign-up, no servers. The link is a sample restaurant API; swap in your own API’s address. It prints the MCP address to paste into Claude.
The stack you’d run, and the one you don’t
Writing the MCP server is the small part. Running it safely on the internet takes every layer below, and each one keeps needing attention after launch. Flip the switch to see who runs what.
What people see
What it takes, under the water
- Speak the MCP protocolYou · 3–5 days
- Turn your routes into toolsYou · 2–4 days
- Sign-in that AI clients acceptYou · 1–3 weeks
- Limits for assistants stuck in a loopYou · 1–2 days
- A record of every callYou · 1–2 days
- Versions and rollbackYou · 2–3 days
- Scaling for traffic spikesYou · 1–2 days
- HTTPS and a domainYou · 2–4 hours
- Servers to run it onYou · 1–2 days
Times are rough estimates for one experienced developer, including testing. They cover building it once; patching, scaling and watching it afterwards is ongoing work on top.
Every MCP version, every client
MCP is the language AI assistants use to talk to your server, and it has been updated four times since it launched in late 2024. Each assistant speaks the version it was built for, and a server that doesn’t speak that version can’t connect to it. APIblaze speaks every version, so Claude, Cursor, Codex and the rest all connect.
- 2024-11-05the first
- 2025-03-26supported
- 2025-06-18supported
- 2025-11-25supported
- 2026-07-28latest
From your API to Claude, start to finish
Start from wherever your API is today. Once it is live, every call an assistant makes goes through the same checks, and none of them run on your servers.
Start from wherever your API is
APIblaze runs the MCP server; your API stays where it is. Pick the one that matches yours.
Your API is deployed somewhere. Point APIblaze at its address or its OpenAPI description.
$ npx apiblaze@latest create --target https://ninopizzas.com/openapi.yamlPrints an MCP address to paste into Claude, Cursor or Codex.
What happens on every call
Ana asks Claude for her bookings at a restaurant whose API runs on APIblaze.
Ana asks Claude: “show my bookings”
- tools/call list_bookingsfrom Claude, for Ana
- Signed inAna, through GitHub
- Allowedcustomers see their own bookings
- Under the limitwell inside 10 a second
- Your APIone ordinary GET /bookings
- Answeredher 2 bookings, back to Claude
- Loggedwho, what, the answer, how long
Sign-in, rules and limits run in APIblaze
On Cloudflare’s network, close to whoever is calling. Your API only sees requests that passed.
Your API gets one ordinary request
No MCP code in it, no session handling, no token checks. It answers the way it always has.
Every call leaves a record
Who asked, for what, the answer and how long it took, ready when something looks wrong.
Same server, two very different mornings
Most hosting puts your MCP server on the internet and stops there. Here is the same morning of calls, against a server hosted bare and the same server on APIblaze.
APIblaze hosts it with the safety built in.
Hosted bare
online, and nothing else
- 09:14
Unknown callercancel_booking
Done. A stranger cancelled a booking.
- 09:15
Unknown callerlist_bookings
Every customer’s bookings, handed over.
- 09:20
Agent in a looplist_bookings ×1,200
Server overwhelmed.
- 09:31
Ana, via Claudelist_bookings
Timed out. Ana can’t get in.
1 booking gone · everyone’s data out · Ana locked out · no record of any of it
Hosted on APIblaze
sign-in, rules, limits and a log on every call
- 09:14
Unknown callercancel_booking
401 · sign in first
- 09:15
Unknown callerlist_bookings
401 · sign in first
- 09:20
Agent in a looplist_bookings ×1,200
429 · slowed to 10 a second
- 09:31
Ana, via Claudelist_bookings
200 · her 2 bookings
2 strangers stopped · 1 loop slowed · Ana served · every call on record
Common questions
How do I host a remote MCP server without running infrastructure?
Put APIblaze in front of your API. One command gives you a live MCP address on Cloudflare’s global network, with sign-in, rules, limits and logs built in, and no servers, containers or certificates for you to manage.
What is a remote MCP server?
An MCP server that AI assistants reach over the internet by its address, instead of one that runs on the same computer as the assistant. Claude’s custom connectors, for example, connect to remote servers.
Do I still need to host my API?
Yes. APIblaze runs the MCP server and everything in front of your API, not the API itself, which can live anywhere with an address: a cloud function, a container or a service you already run. While you build, the dev command serves it straight from your laptop.
Which AI clients can connect?
Any MCP client, including Claude, Cursor and Codex. APIblaze speaks every MCP version from 2024-11-05 to today’s, so a client pinned to an older version still connects.
Can I use my own domain?
Yes. Keep the address APIblaze gives you, or bring your own domain: APIblaze shows the DNS records to set and manages the certificates.
What does it cost?
There is no subscription and no monthly minimum. You pay per request from prepaid credits, with sign-in and permissions included in the price.
Can I try it without an account?
Yes. The command works without signing up. Claim it to an account within 30 days to keep it.
Prices are on the pricing page.
Put your MCP server online now
One command, no sign-up, nothing to keep running. Sign-in, rules, limits and logs included.
$ npx apiblaze@latest create --target https://ninopizzas.com/openapi.yaml