CLAUDE CODE DEPLOYMENT GUIDE

Deploy an app with Claude Code via MCP

Connect Claude Code to Yeeted AI when you want the same agent that writes your application to deploy and verify it. Yeeted returns structured deployment, health, log, and rollback results that Claude Code can use in its next step.

Add Yeeted to your MCP configuration

{
  "mcpServers": {
    "yeeted": {"type":"http","url":"https://mcp.yeeted.ai/mcp"}
  }
}

Restart or reload Claude Code after adding the server. The first connection starts browser-based authorization. You need an existing Yeeted beta account with an invite code and verified email.

Prompts that create a safe deployment loop

“List the Yeeted tools and inspect the project context.”
“Deploy this app to a development preview and run the smoke test.”
“Diagnose the failed build; only change application code if the error is self-fixable.”
“Promote the tested preview to production.”
“Roll back app code to the before-payments checkpoint, or use a retained git hash.”

Start in a preview. Production needs the Small Business plan or higher (after the beta); every plan can deploy previews. Promotion ships the same tested image, avoiding a rebuild between validation and production. Add a yeeted.yaml only when auto-detection needs explicit port, health-check, environment, database, or dependency settings.

A git-hash rollback restores app code only; database changes are not automatically rolled back. A named production checkpoint with a captured database snapshot can also restore supported production data except Redis on plans with snapshots if the restore succeeds. Check the rollback result. Keep source and database backups outside the beta service. Do not send secrets or proprietary code that you cannot afford to expose.

More deployment help

See the MCP deployment overview and the complete Yeeted AI docs.