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.
1.6 s
cold start, measured in production
0.8 MB
deploy artifact — no Docker image
2
regions: mx-central-1 · us-east-1
$0
while your server sleeps
Built security-first, from day one — not patched in later.
❯ runscale deploydeploying my-server (sovereign)building bundle...48.2 KiB, sha256 3f9c21ab04e1…✓ validate✓ provision✓ health✓ releaselive: https://…mx-central-1.amazonaws.com/mcp/
Deploy
Bundle, upload, provision, health check, release. Every stage streams to your terminal and to the dashboard.
Features
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 })Runtime
A three-line adapter wraps the official SDK. Secrets arrive as environment variables at runtime; nothing else changes.
Features
Mexico (Central)
mx-central-1
Querétaro · data residency
52 ms
warm request from MX
1.6 s
cold start
US East
us-east-1
N. Virginia · next to the model hosts
300 ms
warm request from MX
2.1 s
cold start
Residency
Querétaro for regulated workloads, N. Virginia for everyone else. Logs, secrets and metrics never leave the server's region.
Features
No Dockerfiles, no YAML, no infrastructure to babysit.
$ runscale init my-serverOne manifest, one entrypoint. Already have an MCP server? Point the manifest at your code.
$ export RUNSCALE_API_KEY=…Create a key in the dashboard. Deploy keys can ship code — they can never destroy infrastructure.
$ runscale deployBundle, upload, blue/green release. The command streams every stage and ends with your live endpoint.
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 specUsage-based, with no minimums. While we are in early access, deploying is free.
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.
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.
You pick the region once, per server. Querétaro, Mexico (mx-central-1) keeps your server, its secrets and its logs in-region for regulated workloads. N. Virginia (us-east-1) runs the same engine closest to the model hosts, with cheaper compute and no residency claim. Residency is a choice you make, not a limitation.
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.
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.
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.
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.
Create your organisation and deploy in the next ten minutes.