Log inSubmit server
Clize logo

Clize

Hosted CLI and MCP tools for domains, email, static deployments, payments, and media generation.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Clize

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "clize": {
      "command": "npx",
      "args": [
        "-y",
        "-p",
        "@clize/clize",
        "clize-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 33 tools correctly (21d ago).

Overview

The Clize MCP server gives AI coding agents access to hosted actions for domains, email, deployments, payments, and media generation. It works as part of the Clize CLI, which connects to Clize's control plane rather than requiring Cloudflare or Vercel credentials on the local machine. Use it when an agent needs to register a domain, operate an inbox, publish a static site, generate media, or handle customer payments. Claude Code and Codex are explicitly supported through the installation workflow.

Use cases

  • Claim a free project identity and mailbox
  • Read verification codes from an agent inbox
  • Deploy a static site from a local directory
  • Send approval-controlled transactional email
  • Generate hosted images for a project

Key features

  • Domain claiming, search, purchase, and import
  • Hosted inboxes with search and verification-code polling
  • Human-approved email outbox
  • Directory-based static site deployment
  • Hosted image generation with references and masks
  • CLI installation and MCP registration

Tools33

What Clize lets your agent do. Expand a tool for its parameters.

Verified live~4.2k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

11/11 checks healthy over the last 91d

What it can do

From the 33 tools this server returned when we ran it.

Can delete or modify data · 2Handles credentials · 1Makes network requests · 3Read-only tools · 31
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age136 days
Maintainers1

Observed 2026-10-19 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 4d ago via OSV.dev · @clize/clize (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads2.1kPackage downloads in the last 30 days.
Last commit1mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed33Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Clize works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Clize

Clize is an MCP server that connects AI coding agents to Clize's hosted control plane for domains, email, deployments, payments, and media generation. Its main tools cover claiming and managing domains, reading and sending email, deploying static sites, and generating media without requiring local Cloudflare or Vercel credentials.

Install it with `npm i -g @clize/clize`, then run `clize install --mcp`. The installer registers the `clize-mcp` server and installs the agent skill; use `--claude` or `--codex` to scope installation, or `--dry-run` to preview changes.

Run `clize deploy <dir>` after logging in and, when needed, bind the directory with `clize init --handle <slug>`. The deployment publishes a multi-file static site to a free Clize handle or a whole domain in the account.

Email sent without `--confirm` goes to an approval outbox by default. A person can approve or reject it in the console or through a signed digest link, while standing allowlists are managed only in the console and cannot be granted by CLI-issued keys.

Related MCP servers

All in Coding Agents All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewClize AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/clize?style=directory)](https://allmcps.com/mcp/clize)
HTML Embed
<a href="https://allmcps.com/mcp/clize"><img src="https://allmcps.com/api/badge/clize?style=directory" alt="Clize on AllMCPs" /></a>