# Clize

> Clize is a CLI and MCP server that gives AI coding agents real-world actions: domains, email, deploys, payments, and media generation. From inside Claude Code, Codex, and other agents it registers and buys domains, sets up real send-and-receive email (like support@yourdomain), deploys sites, takes payments through Stripe, runs an email-based support or onboarding desk, clears email-verification gates when signing up for other services, and generates images, video, and music. You and the agent never hold any model, cloud, or provider API keys — Clize is the hosted hands.

Clize is the hands; your agent stays the brain. The agent understands, decides, and writes the prompts; Clize carries out the domain, email, deploy, payment, and media actions in the real world. Install once and it wires into Claude Code and Codex as a skill (default) or an MCP server (opt-in).

## Start here

- [Clize — real-world hands for your AI agent: domains, email, deploy](https://clize.ai/): Real-world hands for your AI agent: in Claude Code or Codex, Clize buys domains, sends and receives email, ships sites, and runs email support. CLI and MCP.
- [MCP server for real-world AI agent actions](https://clize.ai/mcp-server-real-world-actions/): Most MCP servers expose data. Clize exposes carefully gated real-world actions: domains, email, deploys, status, billing, and customer workflows for AI agents.
- [Best MCP servers for builders: read-only to action](https://clize.ai/best-mcp-servers/): The best MCP servers, grouped by what your agent actually does — docs and code, browser and data, SEO and analytics, automation, and real-world actions.

## Products

- [Agent Inbox by Clize: email API for AI agents](https://clize.ai/inbox/): Agent Inbox gives your AI agent a real email inbox: send with human approval, receive untrusted-by-default, pass verification gates. CLI + MCP, by Clize.
- [Best email API for AI agents (2026): 7 compared](https://clize.ai/inbox/best-email-api-for-ai-agents/): AgentMail, Agent Inbox, Nylas, Resend, Postmark, SES, or DIY Gmail? An honest comparison of email APIs for AI agents — by what your agent actually does.
- [Agent Storefront by Clize: your AI agent runs the store](https://clize.ai/storefront/): Agent Storefront lets your AI agent run a real store: checkout, orders, refunds, shipping and a support inbox — with the money gate in your hands.
- [Sell with an AI agent: quote to delivery, one thread](https://clize.ai/storefront/sell-with-an-ai-agent/): A full merchant walkthrough: publish a catalog, take the payment, source and ship the order, notify the buyer, refund when it goes wrong — real commands.
- [Agentic commerce for merchants: ACP, UCP, AP2](https://clize.ai/storefront/agentic-commerce-for-merchants/): ACP, UCP, AP2 and x402 read from behind the counter: what each protocol settles, what it asks of a seller, and what to do about it today.
- [Sites by Clize: ship a real site from Claude Code](https://clize.ai/sites/): Your coding agent writes the marketing site; Clize puts it live — real domain, HTTPS, and an inbox that receives. One run from Claude Code or Codex.
- [Build a website with Claude Code (and put it live)](https://clize.ai/sites/claude-code-website/): Build a website with Claude Code and actually ship it: design method, agent-written code, local preview, then a live HTTPS domain with a working inbox.
- [Lovable alternatives (2026): 8 honest options](https://clize.ai/sites/lovable-alternatives/): v0, Bolt, Replit, Dyad, WeWeb, Webflow AI, Sites by Clize or DIY? Eight honest Lovable alternatives, compared by what you are actually building.
- [Agent Domains by Clize: buy, point, and monitor](https://clize.ai/domains/): Agent Domains gives your AI agent domains it can buy, point, and monitor — four-layer health checks and alerts included. CLI + MCP, by Clize.
- [Domain health check: four layers, one command](https://clize.ai/domains/domain-health-check/): Four layers decide whether a domain works: registry delegation, DNS zone, binding, content. How each breaks, how to test with dig, and the one-command version.
- [Programmatic domain registration (2026): 5 compared](https://clize.ai/domains/programmatic-domain-registration/): Cloudflare Registrar API, Name.com, Namefi, DNSimple, or Agent Domains? An honest comparison of registrar APIs for programmatic and agent-driven registration.
- [llms.txt: what it is, and how to generate one](https://clize.ai/seo/llms-txt/): What the llms.txt spec requires, honest evidence on whether anything reads it, what changed in v2, and how to generate one from your sitemap inventory.
- [GEO tools (2026): 8 AI visibility platforms compared](https://clize.ai/seo/geo-tools/): Profound, Semrush, SE Ranking, Ahrefs, Otterly, LLMrefs, AIclicks, AthenaHQ — compared honestly, plus why every GEO tool stops short of changing your site.

## Set up Clize in your agent

- [Add Clize MCP server to Claude Code (step by step)](https://clize.ai/claude-code-mcp-setup/): Add Clize as an MCP server to Claude Code, step by step: install, log in, connect with one command, verify with claude mcp list, then set up a support inbox.
- [Set up Clize MCP in the Codex CLI (step by step)](https://clize.ai/codex-cli-mcp-setup/): Add Clize as an MCP server to the Codex CLI, step by step: install, log in, connect with one command, verify with codex mcp list, then run a real action.
- [Claude Code MCP server for real-world agent actions](https://clize.ai/claude-code-mcp/): Use Clize as a Claude Code MCP server to connect domains, inboxes, deploys, billing, and support workflows — through a Skill, a CLI, and MCP.
- [Codex CLI MCP server for domains, email, and deploy](https://clize.ai/codex-mcp/): Clize connects the Codex CLI to real-world actions via an MCP server: buy domains, send and receive mail, deploy sites, and check status — with safety gates.

## Compare

- [Claude Code vs Codex: which coding agent?](https://clize.ai/claude-code-vs-codex/): Claude Code vs Codex, compared honestly: what they share, where they differ, and how to choose — plus how both reach the real world through MCP.
- [Zapier alternatives for AI agents](https://clize.ai/zapier-alternatives/): Zapier alternatives for AI agents: how no-code automation like Make and n8n compares to giving your agent tools it calls directly via MCP, and where Clize fits.
- [Top AI agent platforms, by what they do](https://clize.ai/top-ai-agent-platforms/): Top AI agent platforms mapped by job: orchestration frameworks, coding agents, tool-calling and integration layers, sandboxes, and real-world action layers.

## What Clize can do

- [AI email agent: give your agent its own inbox](https://clize.ai/ai-agent-email/): Clize turns your coding agent into an AI email agent — a real inbox it can send from and receive into, with drafts, human approval, and support context.
- [AI customer support agent with an inbox + your docs](https://clize.ai/ai-customer-support-agent/): An AI customer service agent that reads customer emails, uses your docs, and drafts replies you approve — customer support automation without a full helpdesk.
- [AI agent deployment: generated site to live domain](https://clize.ai/ai-agent-deployment/): AI agent deployment with Clize: your coding agent ships a static site to a live domain over HTTPS — buy the domain, point DNS, deploy, behind safety gates.
- [Stripe MCP payments: gated payment links for agents](https://clize.ai/stripe-mcp-payments/): Let Claude Code or Codex create gated Stripe payment links — clear quotes and human confirmation before money moves, into Stripe Connect or Clize balance.
- [AI agent media generation for Claude Code and MCP](https://clize.ai/ai-agent-media-generation/): Let Claude Code, Codex, or any MCP agent generate images, video, and music with no model keys of your own — files and URLs ready to deploy or attach.
- [AI agent CLI your coding agent reaches for](https://clize.ai/ai-agent-cli/): Clize is an AI agent CLI your coding agent calls to claim handles, buy domains, send email, and deploy — available as a CLI, a Skill, and an MCP server.
- [AI agent infrastructure for real-world actions](https://clize.ai/ai-agent-infrastructure/): AI agent infrastructure is more than orchestration — it's identity, an inbox, domains, deploy, billing, and the safety gates your agent acts through.

## Use cases

- [Let your AI agent send email (with an approval gate)](https://clize.ai/use-cases/agent-send-email/): Give Claude Code or Codex an inbox it can send from through Clize — the agent drafts, you approve, Clize sends. Real email, with an outbound approval gate.
- [Deploy a website straight from Claude Code or Codex](https://clize.ai/use-cases/agent-deploy-site/): Your coding agent builds a static site and ships it to a live domain over HTTPS through Clize — buy the domain, point DNS, deploy — behind safety gates.
- [AI agent email verification: clear the sign-up gate](https://clize.ai/use-cases/agent-email-verification/): When your AI agent signs up for a service, Clize's real inbox receives the verification code so the agent can read it and continue — the identity gate, handled.
- [Triage a support inbox with an AI agent](https://clize.ai/use-cases/triage-support-inbox/): Point an agent at a real support inbox through Clize: it reads incoming mail, uses your docs, and drafts replies you approve before anything sends.
- [Create a Stripe payment link from your AI agent](https://clize.ai/use-cases/agent-payment-link/): Your agent drafts a quote, you confirm the amount and purpose, and Clize creates a Stripe payment link — the money gate stays in your hands.

## Writing

- [Blog · Clize — notes on giving AI agents real-world hands](https://clize.ai/blog/): The Clize blog — notes on giving AI agents real-world hands: email, domains, deploy, identity, and continuity for agents in Claude Code and Codex.
- [Why your AI agent is trapped in a sandbox — and what to do about it](https://clize.ai/blog/why-ai-agents-are-trapped-in-a-sandbox/): AI agents can build the whole product but can't reach the world it ships to. The three things every agent is missing: hands, identity, and continuity.
- [MCP servers that give your AI agent real-world hands](https://clize.ai/blog/mcp-servers-real-world-hands/): Most MCP servers let your agent look things up. The ones that matter let it act — buy a domain, send email, ship a site. What an action-MCP must get right.
- [Why your AI agent needs an email address of its own](https://clize.ai/blog/why-your-ai-agent-needs-its-own-email/): Before more intelligence, an agent needs an address. Why your AI agent should have its own inbox — not yours — and the two safety gates you can't skip.
- [Customer support without a helpdesk — just an agent and an inbox](https://clize.ai/blog/customer-support-without-a-helpdesk/): You don't need Zendesk to answer customers: just an inbox your agent can read and your docs. The lightweight shape of support, and two lines you don't cross.
- [Letting your agent clear its own gates — and where to draw the line](https://clize.ai/blog/let-your-agent-clear-its-own-gates/): An agent with its own inbox can clear 'verify your email.' Useful — and exactly where you stop. Light gates vs. heavy gates, and where to draw the line.

## Optional

Clize's site is also published in 10 languages (English, Simplified/Traditional Chinese, Japanese, Korean, Spanish, French, German, Italian, Arabic). The full multilingual URL list lives in the sitemap.

- [Sitemap](https://clize.ai/sitemap.xml): every public URL, all locales