Deploy Claude Code Apps to Production

To deploy apps to production with Claude Code—or any coding agent—you must connect the agent to a cloud platform via the Model Context Protocol (MCP). By connecting Claude Code, Cursor, or your custom AI agent to the Scalix MCP server, the agent can autonomously apply migrations to your ScalixNova database, deploy your container, and return a live URL in one session.

Claude Code writes the code. Scalix ships it. The missing connection is the Model Context Protocol.

The deploy gap

You use Claude Code to scaffold a project, write handlers, fix bugs, and add tests. The app runs on your laptop. Then you hit the wall: the agent can write the code but cannot ship it. Deploying means talking to a cloud: migrating database schema, pushing a container, wiring environment variables, checking health. Those are actions on a system outside your repository. The agent has no tools for them, so it writes a deploy script and asks you to run it.

The fix is not a better script. The fix is giving the agent real tools for your cloud.

Connect Claude Code to Scalix MCP

One command, one API key:

claude mcp add --transport http scalix https://api.scalix.world/v1/mcp \
  --header "Authorization: Bearer $SCALIX_API_KEY"

Then claude mcp list confirms the connection. Inside a session, /mcp shows the tools. The agent now has 50+ cloud tools across database, compute, storage, auth, AI inference, billing, and logs, all behind one key, one gateway.

The deploy walkthrough

You have an app in your repo. The Scalix MCP server is connected. In the session, ask:

Deploy this app to Scalix Run. It listens on port 8080. Connect to my Postgres database, pass the connection string as an environment variable, and give me the URL.

The agent executes through MCP tools in order:

1. Database migrations: The agent inspects the ScalixNova database schema and safely applies versioned migrations via the platform API. Destructive queries wait for your confirmation.
2. Deploy service: scalix_run_deploy builds from source (auto-detects Node, Python, Go, Rust, or Dockerfile) or uses your image. Wires the DATABASE_URL env var. Returns a stable URL: https://my-app.run.scalix.world.
3. Verify: scalix_run_status checks health. scalix_run_logs streams logs if needed.

The equivalent CLI (the agent runs the MCP equivalent):

scalix-cloud run deploy --name my-app \
  --image api.scalix.world/<project-id>/my-app:v1 \
  --port 8080 \
  --env DATABASE_URL=postgres://... \
  --min-instances 1 --max-instances 5

You did not run it. The agent did. When it finishes, the service is live at https://my-app.run.scalix.world.

Safe migrations and schema management

Before applying schema updates, the agent uses database tools to inspect and safely migrate:

# Agent inspects schema and applies versioned migration
tool: scalix_db_migrate
args: { "version": 42 }

Destructive queries (such as DROP or TRUNCATE) require a two-step confirmation token at the gateway layer, ensuring the agent cannot execute unconfirmed destructive commands against production tables.

The agent observes, fixes, redeploys

This loop is the difference between a script and a shipper:

1. Agent deploys.
2. Agent reads back status and logs (scalix_run_status, scalix_run_logs).
3. If deploy fails or health check fails, agent sees the error.
4. Agent patches the code.
5. Agent redeploys.
6. Loop until healthy.

You do not switch terminals. You do not copy logs. You describe the outcome; the agent operates the cloud.

Human-in-the-loop guardrails

Routine operations (dev deploys, reads, queries, dev resources) run freely. Consequential actions pause for your approval:

• Production deploys
• Database deletes
• Spend past configured caps
• Auth changes on live services

The agent prepares the action, presents context, and waits for your one-tap approval. Budget caps are enforced at the platform level; the agent cannot silently exceed them. API keys scope to specific services and actions (a CI/CD key might deploy and read logs but never touch databases).

What the agent needs from you

• A Scalix API key (generate in console, pass as Bearer token when adding MCP server)
• The app repo (local or GitHub — the agent clones it)
• Port the app listens on (or the agent detects it)
• Optional: custom Dockerfile if you need a non-standard build

Try it

Generate an API key at Scalix Console. Connect Claude Code:

claude mcp add --transport http scalix https://api.scalix.world/v1/mcp \
  --header "Authorization: Bearer $SCALIX_API_KEY"

Describe what you want live. The agent configures, deploys, and hands you the URL.

Check out the pricing page for current rates.

Questions on Discord or DM on X.