Clize

What Clize MCP server does

The Clize MCP server exposes Clize's hosted real-world actions to coding agents. Its supported areas include domain identity and registration, email, static website deployment, payments, and media generation. The same product is also available through the clize command-line interface, so teams can use shell commands for scripted workflows and MCP for agent-directed actions.

Domain workflows include claiming a free <slug>.clize.app identity, searching available top-level domains, buying or importing a domain, listing domains, and checking domain configuration. A claimed identity can also receive a mailbox such as support@<slug>.clize.app when email is enabled.

Email features cover inbox reading, waiting for verification messages, searching and viewing messages, thread access, triage correction, attachments, sending, mailbox creation, forwarding, member access, and scoped email keys. Messages sent without --confirm can enter an approval outbox for human review. Static content can be deployed from a directory to a Clize handle or domain. The product description also includes payment collection and media generation as supported action areas.

How it works

The Clize MCP server and CLI act as thin clients. Commands communicate with the Clize control plane, while domain, email, deployment, and media resources run on Clize infrastructure. Local users do not provide Cloudflare or Vercel keys; bring-your-own provider configuration is handled in the Clize dashboard.

Install the package globally with npm, then run clize install. The installer writes the agent skill that explains when Clize should be used and can optionally register the MCP server with --mcp. The skill is detected for Claude Code and Codex, with scope options for those agents. A directory can be associated with a handle using clize init --handle, allowing deployment and email commands to infer the relevant domain and sender from clize.json.

Setup and configuration

Authentication starts with clize login, which opens browser authorization, or with clize login --token for CI and headless use. clize check verifies login status. clize claim <slug> --email creates a free handle and receiving address; clize domain buy and clize domain import handle custom domains.

Use clize update to refresh the installed release and skill, clize update --check to check without updating, and clize doctor to inspect version drift, skill state, and control-plane reachability. Output is English by default. Setting CLIZE_LANG=zh, or using a Chinese system locale, switches CLI, MCP descriptions, and control-plane messages to Chinese.

Tools and capabilities

The Clize MCP server supports agent workflows involving:

• Claiming identities and managing domains.
• Creating mailboxes and reading verification codes.
• Sending email with explicit confirmation or human approval.
• Deploying multi-file static sites from a directory.
• Generating images, including reference-image, masking, and composition workflows.
• Managing hosted actions across multiple projects under one account.

Image generation may run asynchronously. gpt-image-2 tasks can take minutes, and the CLI can wait for completion or return a task for later retrieval. Reference-image limits and file-size limits depend on the upstream model.

Limitations and notes

The Clize MCP server is opt-in during installation because its tool list remains in the agent's context each session. Free-tier quotas apply to handles, mailboxes, claims, outbound email, deployments, and site storage; over-limit requests return HTTP 429 without charging.

Email sending has safety controls. Without --confirm, a message waits for approval unless an applicable console-managed allowlist permits it. CLI-issued keys cannot create approval exemptions. Domain purchases made through Clize use Clize's registrant contact; users who need to be the registrant of record should register elsewhere and import the domain.

A deployment target is a free handle or an entire domain. A subdomain such as blog.example.com is not currently treated as a separate deployment target. Some country-code TLDs are unavailable through Clize, and clize domain tlds lists the supported choices.