NitroStack
01
What you get
NitroStack is how a team goes from a tool written in code to an MCP server it can host. You can build that server in TypeScript or Python. The SDK, CLI, and widgets are open source. Studio and Cloud sit on top when you want to test a call and ship it.
- TypeScript or PythonThe same product covers both. Your team writes the tools in the language it already ships in, instead of splitting the server across two stacks.
- Open source to startThe SDK, the CLI, and the widgets are open source on GitHub. You can read the code, run a server locally, and star the repo. NitroStudio and NitroCloud are the products around that core.
- Try a tool before customers see itNitroStudio is where you run a call and read the result. You do that before the server has a public URL.
- Hosting is includedNitroCloud deploys the server. That includes push-to-deploy, scale-to-zero, custom domains, and TLS.
02
How you build
Pick the language your team already uses. The CLI scaffolds the server. A small server is just the tools your product already knows how to do: look up an order, create a ticket, send the update.
npx @nitrostack/cli@1.1.0 init my-server --preset code-modeYou try those tools in NitroStudio, then deploy on NitroCloud. Customers reach one server. The hosting page is that step on its own.
03
What Code Mode changes
Every tool you add is another item the agent has to read before it does any work. A long list makes each conversation more expensive, and it makes the wrong tool more likely. That is a cost problem, not a coding style problem.
Code Mode keeps that list off the conversation. The agent writes a short program. Your server runs the steps. The agent receives the answer, not every row in between. A handful of tools does not need this. Turn it on when the list itself is the bill.
The Code Mode page shows the same idea in more detail, including the walkthrough.
04
How it compares
This is a map of who builds the server, not a benchmark. Manufacturing one from the official SDK means you wire the transport, the auth, and the host yourself. The other columns are the frameworks and companies people actually start from.
| NitroStack | Official MCP SDK | FastMCP | Cloudflare | |
|---|---|---|---|---|
| What it is | Open source SDK for TypeScript and Python, plus Studio and Cloud | The protocol library. You manufacture the rest | A Python framework for MCP servers | Agents SDK and hosting on their edge |
| Language | TypeScript and Python | TypeScript | Python | TypeScript on Workers |
| Test a tool call | NitroStudio | You bring a client | You bring a client | Their dashboard and a client |
| Deploy | NitroCloud, or your own host | You host it | You host it | Cloudflare |
| Code Mode | On when the tool list gets expensive. The agent only sees the final answer | Not a Code Mode product | A Python CodeMode transform in FastMCP 3.1 | They named the pattern. V8 isolate, often search and execute |
| Pick it when | You want the path from tool code to a hosted server | You want the protocol and will assemble transport, auth, and hosting | The server is Python | The server already lives on Cloudflare |
A page for each competitor, including Speakeasy, Alpic, and the rest of this table.
FastMCP's Code Mode ships in 3.1 as a Python transform. Cloudflare's write-up is their measurement of their API, not a NitroStack benchmark. Anthropic's engineering post is the model-lab version of the same pattern.
Ask the team for a free POC.
Submit a request for a free POC with our team. Send it whether you need one or not. We will tell you if NitroStack fits the server you want to build.