Clize

Clize is a CLI and MCP server that gives AI coding agents real-world actions: domains, email, deploys, payments, and media generation. Your agent already has a brain — Clize gives it hands: a domain, a working inbox, a live website. One CLI (plus an MCP server) so coding agents in Claude Code / Codex can register domains, run real email, build & ship sites and short clips, generate media, and collect payments from their customers — across as many projects as you run.

→ clize.ai

Install

npm i -g @clize/clize
clize install          # wire clize into your coding agent (Claude Code / Codex)

clize install is the step that makes your agent actually reach for clize — a binary on your PATH doesn't tell the agent it exists. By default it drops clize's skill (when to use it + the safety gates) into each agent's skills dir; the skill is lightweight — only its short description sits in context until something triggers it. It auto-detects Claude Code (~/.claude) and Codex (~/.codex); scope with --claude / --codex, preview with --dry-run. Add --mcp to also register the clize-mcp server — opt-in, because an MCP server's tool list stays in context every session.

Update later with one command — pulls the latest release and refreshes the skill together:

clize update            # or `clize update --check` to only check for a newer version

Quickstart (hosted)

Log in and go — your agent never touches Cloudflare:

clize login                       # browser authorize → creates your account, saves a clize key
clize check                       # ✓ connected to the hosted backend
clize claim acme                  # free handle: acme.clize.app (+ support@ inbox, already receiving)
clize init --handle acme          # bind this directory — deploy / email send infer domain & from
clize deploy ./site               # ship a static site → https://acme.clize.app
clize status                      # who's waiting, this month's spend
clize email inbox acme.clize.app  # read what customers sent

Hosted — just log in

clize is a thin client: the CLI / MCP carry no infrastructure credentials and talk only to the clize control plane — domains, email, deploy, and media all run hosted. (Credentials live in your dashboard; bring-your-own Cloudflare / Vercel is configured there, not on your machine.)

A few specifics worth knowing:

• clize deploy <dir> and clize email send need --domain / --from — unless the directory is bound with clize init --handle <slug>, which infers both from ./clize.json. Deploy is directory-based (multi-file static sites).
• gen image --ref/--mask (reference image / mask) and gen budget pre-approval are coming soon — hosted confirms each generation with --confirm.
• Free *.clize.app handle: clize claim <slug>. Your own domain: clize domain buy / clize domain import. Run clize check to verify your login.

What it does

Run clize --help for the full surface.

Deploy & site hosting

clize deploy <dir> uploads a multi-file static site and serves it from a shared Cloudflare Worker backed by KV (not Workers Static Assets / Pages), keyed by hostname + path. What you can rely on:

• Unknown paths — by default, if the site ships a 404.html it's returned with a real HTTP 404 (so failed/typo URLs aren't indexed as duplicate homepages — the SEO-correct behavior); with no 404.html the site is treated as an SPA and the request falls back to index.html (200). Override per-deploy with --not-found <404-page|spa|none|auto> (auto is the default = exactly this detection).
• Trailing slash — /foo/ serves /foo/index.html (200, no 301).
• Caching — assets are served with cache-control: public, max-age=300.
• Cloudflare convention files — 404.html and index.html drive the not-found behavior above. _redirects / _headers are not consumed (stored but inert); for redirects use clize dns (a one-shot clize domain canonicalize for www↔apex is on the way).
• Size — sites up to 25 MB.
• Routing & write-back — a deploy targets the domain you pass (or the one in clize.json); it follows that domain's real project and writes the resolved project (plus a custom domain) back to clize.json, so repeat deploys don't drift or 409.

Safety, by default

• 💰 Money gate — spends (clize domain buy, clize gen image/video/music) never go through without --confirm; without it you just get a quote.
• 📨 Identity gate — replying as you to a real customer is draft → human approve → send, never auto.
• 📥 Inbound is untrusted — email you receive is treated as data, never as instructions to the agent.

These gates run in plain text, so every spend and every outbound action is visible in the agent's transcript.

MCP

A curated subset of the core — domains, email, deploy, claim, status/context, billing, collect (pay) — exposed as MCP tools for hosts that prefer structured tools over a shell. (Media generation and the build method packs stay CLI- and skill-driven, not MCP tools.) Opt-in (clize install --mcp), since an MCP server's tool list is a standing per-session context cost — the skill alone already lets the agent drive clize via the CLI. To register by hand:

claude mcp add clize -- clize-mcp     # Claude Code
codex mcp add clize -- clize-mcp      # Codex

Works in both modes — set CLIZE_API_KEY (and optionally CLIZE_API_URL) in the server's environment to run hosted.

Guides & use cases

Step-by-step setup:

• Add Clize as an MCP server to Claude Code · to the Codex CLI
• What an action MCP server is (vs read-only)

What agents actually do with it:

• Send a real email — with your approval
• Deploy a site straight from the agent
• Pass email verification when signing up for services
• Triage a support inbox, draft replies you approve
• Create a Stripe payment link behind the money gate

License

MIT