Build & deploy an app

This is the full lifecycle of a Cloudrizz app, expressed as MCP tool calls. In normal use you never call these by hand — you describe what you want and the assistant calls them. This page documents the order and intent so the assistant gets it right.

1 · Scaffold

Every app starts with create_app_scaffold. It creates the app inside your organization and lays down a starter project — a static frontend plus an api/*.js backend running on the edge, with the platform bindings (env.AUTH, env.DB, env.STORAGE, env.EMAIL) already available.

  • create_app_scaffold — create the app and its main branch.
  • list_files / read_file — inspect what was generated.

2 · Edit & version

Code changes are made with edit_file, then snapshotted with save_version — that's a commit. Versioning is built in, so every deploy is reproducible and you can roll back.

  • edit_file — write or modify a file in the working tree.
  • save_version — commit the current state as a new version.
  • list_versions — see the version history.
  • list_migrations — review database migrations the app defines.
The _cr_* table prefix in an app's database is reserved by the platform (it backs env.AUTH and friends). Your app defines its own tables; it can't write to the reserved ones.

3 · Branch & preview (optional)

For larger changes, work on a branch so you can preview without touching production. A branch deploys against its own throwaway database, so a work-in-progress can't corrupt live data.

  • create_branch — start a branch off main.
  • describe_branch_intent — record what the branch is for.
  • open_pull_request · list_pull_requests · get_pull_request — propose the change for review.
  • analyze_merge_risk · generate_merge_candidate — let Cloudrizz assess and resolve a merge.
  • merge_pull_request · close_pull_request — land or drop it.
  • reset_playground — wipe a branch's preview database.

4 · Configure resources & secrets

Apps get a database and storage by default. Attach more, and set the environment variables your code reads at runtime.

  • list_resources · attach_resource · detach_resource — manage the database, storage, AI, and other bindings.
  • set_app_env · list_app_env · delete_app_env — manage environment variables (secrets are encrypted and injected at deploy).
  • request_upload_url — get a URL to upload a large asset.

5 · Deploy

deploy_app builds the app and ships it to the global edge. A deploy of main goes to the canonical URL; a branch or preview deploy gets its own preview URL.

https://<slug>.cloudrizz.app
  • deploy_app — build and publish.
  • get_deployment_logs — read build / runtime logs if something fails.

6 · Custom domain

Put the app on your own domain with add_domain. Cloudrizz returns the exact DNS record to add; SSL is issued automatically. The simplest setup is a www subdomain on any DNS provider:

www.example.com   CNAME   <slug>.cloudrizz.app

Apex domains and other providers are supported too — add_domain returns the right records for the option you choose.

7 · Iterate

Keep chatting. Each round is the same loop: edit_file → save_version → deploy_app. Clone an existing app to start from a known-good base with clone_app, and improve search and AI discoverability with update_seo_config.

For the complete list, see the MCP tool reference.