Cloud Overview

Deploy and run your MCP servers on NitroCloud.

NitroCloud is purpose-built for MCP servers. It skips the setup complexity of running your own infrastructure: you connect your code, and NitroCloud builds and runs your server for you.

What you get

One-step deployment

Connect your code, and NitroCloud builds and runs the server for you.

Auto-scaling

Scales automatically with traffic.

Built-in monitoring

Metrics and logs for each deployment.

Automatic SSL

Free HTTPS certificates.

Environment variables

Set secrets in the dashboard, never in your code.

Free tier

No credit card required.

Deploy your first app

You deploy from the dashboard: create an app, link your repository or upload a zip, and add your environment variables. The steps, including how to prepare a TypeScript or Python project, are on the Dashboard page.

How NitroCloud is organized

Everything belongs to an organization. An organization has apps, and each app has an MCP server and a hosted chat.

OrganizationTeams, API keys, integrations, Studio, billing, usage, settings
AppOverview and billing
  • MCP: overview, deployments, logs, monitoring, domains, integrations, settings
  • NitroStack Chat: general, threads, monitoring, analytics, domains, auth, database, AI model, files, settings, danger zone, access

What runs where

An organization is the account boundary. Apps, members, API keys, the GitHub connection, Studio access, and payment methods all belong to the organization.

An app is one product. It can have an MCP server, a hosted chat, or both. The server is what MCP clients call; the chat is a website that calls that server's tools. Each app has its own plan: Free includes 500,000 requests a month, and Pro is billed per app. See App billing.

NitroStudio is separate. It's the desktop app, and organization API keys sign it in. Studio management decides who on the team can use it and which models they can call.

Prefer to host it yourself?

On this page