Agent Inbox MCP server

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 and clize email send need --domain / --from — unless the directory is bound with clize init --handle , 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 . Your own domain: clize domain buy / clize domain import. Run clize check to verify your login.

What it does

Shortened. The full README is on GitHub.