Deploy and scale MCP servers.
From code to a live Model Context Protocol endpoint in minutes. Blue/green releases, a write-only secrets vault, usage-based billing — and data residency you control.
$ runscale deploydeploying my-server (sovereign)building bundle...48.2 KiB, sha256 3f9c21ab04e1…✓ validate✓ provision✓ health✓ releaselive: https://…mx-central-1.amazonaws.com/mcp/
New to MCP?
The Model Context Protocol is the open standard AI assistants — Claude, ChatGPT, Cursor and a fast-growing ecosystem — use to reach tools and data. An MCP server exposes YOUR tools: your database, your API, your business logic. Runscale takes that server from your laptop to a production endpoint any assistant can call — secured, metered and versioned.
Read the MCP specThree commands to production
No Dockerfiles, no YAML, no infrastructure to babysit.
- 01
Scaffold
$ runscale init my-serverOne manifest, one entrypoint. Already have an MCP server? Point the manifest at your code.
- 02
Authenticate
$ export RUNSCALE_API_KEY=…Create a key in the dashboard. Deploy keys can ship code — they can never destroy infrastructure.
- 03
Ship
$ runscale deployBundle, upload, blue/green release. The command streams every stage and ends with your live endpoint.
Your whole server, one file to start
The adapter ships inside the CLI — your project needs nothing from the platform.
import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js'
import { createMcpLambdaHandler } from 'runscale/adapter'
function createServer() {
const server = new McpServer({ name: 'my-server', version: '1.0.0' })
server.tool('hello', async () => ({
content: [{ type: 'text', text: 'hello from my-server' }],
}))
return server
}
export const handler = createMcpLambdaHandler({ createServer })Everything a server needs to live in production
Built security-first, from day one — not patched in later.
Blue/green releases
Every deploy must pass a health check before it receives traffic. Rollback is one click, not an incident.
Write-only secrets vault
Keys go in; nobody reads them back — not even us. Your server receives them at runtime, decrypted in-region.
Per-server access tokens
Each token opens exactly one server, is shown exactly once, and dies the moment you revoke it.
Usage-based billing
Metered from real invocations and compute time. Pay for what your tools actually run — nothing else.
Runtime logs, in-region
Tail your server from the dashboard or the CLI. The logs never leave the region your data lives in.
Data residency you control
First region live in Querétaro, Mexico — with an audit trail for every action. More regions on the way.
Pricing
Usage-based, with no minimums. While we are in early access, deploying is free.
- Deploy production MCP servers
- Blue/green releases + rollback
- Write-only secrets vault
- Runtime logs and audit trail
- Real usage metering, visible in your dashboard
When billing turns on you will see it coming: the dashboard already shows exactly what your usage would cost, in centavos, before we ever charge a card.
Questions, answered honestly
Do I need to know AWS?
No. You write a TypeScript MCP server and run runscale deploy. Provisioning, releases, scaling to zero and metering are our job — there is no console to learn.
Where does my data live?
The first region is Querétaro, Mexico (mx-central-1): your server, its secrets, its logs and its metadata stay in-region. More regions are on the way — residency is a choice you make, not a limitation.
How are secrets handled?
The vault is write-only: values go in via the CLI or dashboard, encrypted per-organisation, and nobody reads them back — not even us. Your server receives them at runtime, decrypted in-region.
What happens if a deploy goes wrong?
It never reaches users: every release must pass a health check on the staged version before traffic flips to it (blue/green). If something slips through anyway, rollback is one click and takes seconds.
Am I locked in?
No. Your code is a standard MCP server built on the official SDK — it runs anywhere MCP runs. The endpoint speaks standard Streamable HTTP. Leaving is a git push somewhere else; we just think you will not want to.
What is the free tier limit?
During early access, fair use — enough to run real servers with real traffic. Metering is live from day one, so you always see what your usage would cost later.
Your first MCP server, live today.
Create your organisation and deploy in the next ten minutes.