Cloudrizz documentation

Cloudrizz lets ChatGPT and Claude build, version, and deploy real apps for you. You describe what you want in chat; your AI assistant uses the Cloudrizz MCP tools to scaffold the app, write its code, run it on a global edge, and ship it to a real URL — with auth, a database, storage, AI, and payments already wired in.

How it works

Cloudrizz is exposed to AI assistants as an MCP (Model Context Protocol) server. Once you connect that server to ChatGPT or Claude, the assistant gains a set of tools — scaffold an app, edit files, save a version, deploy, attach a domain — and calls them on your behalf as you chat.

You don't install an SDK or run anything locally. The assistant does the work through the tools; Cloudrizz builds and hosts the result. These docs are written for that assistant as much as for you — they describe exactly which tool does what, and the order to call them in.

Quickstart

  1. Connect the Cloudrizz MCP server to ChatGPT or Claude and sign in.
  2. Ask your assistant to build something. Behind the scenes it calls create_app_scaffold to create the app.
  3. As you refine, the assistant uses edit_file and save_version to write and snapshot the code.
  4. It calls deploy_app to ship it to a live <slug>.cloudrizz.app URL, then add_domain to put it on your own domain.
New to this? Start with Connect ChatGPT & Claude.

Keep reading

Connect ChatGPT & Claude

Add the Cloudrizz MCP server to ChatGPT or Claude and authenticate.

Working with your AI assistant

How to describe what you want, iterate, and get good results building apps from chat.

Anatomy of an app

How a Cloudrizz app is laid out: static frontend, api/*.js routes, migrations, and config.

Build & deploy an app

Scaffold, edit, version, preview, and deploy an app end to end over MCP.

Embeddable widgets

Build a widget that embeds on any website with a single <script> tag.

Branches, PRs & AI merges

The collaboration workflow: feature branches, preview deploys, pull requests, and AI-assisted merges.

Teams, roles & permissions

Organizations, owner/admin/member roles, invitations, and who can do what.

MCP tool reference

Every Cloudrizz MCP tool, grouped by what it does.

Platform bindings

The env.* bindings every app gets: database, storage, email, AI, cache, auth, and payments.

Environment variables & secrets

Set config and encrypted secrets with set_app_env; the built-in env.APP_ID and env.ENVIRONMENT.

Database

Your app's SQL database via env.DB, migrations, and the reserved _cr_* namespace.

User accounts & auth

Sign up, sign in, sessions, email verification, and 2FA for your app's users via env.AUTH.

AI

Call OpenAI, Anthropic, and Workers AI from your app via env.AI — managed credits or bring your own key.

Email

Send transactional email from your app via env.EMAIL.

Payments

Charge your app's users with Stripe via env.PAYMENTS — checkout, subscriptions, and webhooks.

File storage

Store and serve files via env.STORAGE, including public file URLs.

Scheduled jobs

Run code on a schedule with api/cron.js and the cron tools.

Custom domains

Put your app on your own domain with automatic SSL.

SEO & AI discoverability

Control how your app appears in search engines and to AI assistants via cloudrizz.seo.json.

Give your app an MCP server

Expose your own MCP tools from your app so ChatGPT and Claude can connect to it, authenticated as your app's end-users.

Limits & quotas

Plan limits, hard caps, and rate limits.

Troubleshooting

Reading deployment logs and fixing common deploy/runtime issues.

FAQ

Common questions about Cloudrizz.