// CLAUDE CODE · MCP

Let Claude Code act outside the sandbox

Claude Code reasons and writes across your repo. Clize gives it real-world hands — domains, inboxes, deploys, and support — through a Skill, a CLI, and an optional MCP server.

Why Claude Code users need real-world actions

Claude Code can plan a product and write every file of it. What it can't do alone is the last step you actually wanted: register the domain, put the site online, and answer the first customer email. Those live outside the repo — and that's the layer Clize adds.

Skill, CLI, and MCP — how they fit

  • Skill — the trigger layer. Claude Code reaches for Clize when a task needs the real world ("ship this", "set up support").
  • MCP — the structured tool layer. Clize exposes domains, email, deploy, and status as typed tools.
  • CLI — the stable operation layer. The same actions run as plain commands when you want determinism or a script.

Set up a support inbox

Tag an inbox as support@, point it at your docs, and the loop runs: Claude Code reads an incoming message, drafts a reply from your docs, you okay it, and it sends — then picks the thread back up next session. See customer support with an agent and an inbox.

Deploy a site

From generated pages to a live domain over HTTPS in one flow — buy the domain, deploy, done. The agent owns the deploy target instead of handing you a zip.

The safety gates

Real-world actions need real guardrails. Clize holds three lines, every time:

  • Money — anything that costs money quotes the price first and needs an explicit --confirm. No surprise charges.
  • Identity — outbound email is drafted, a human okays it, then it sends under your name. The agent never sends unattended.
  • Inbound is untrusted — an incoming email is data to read, never an instruction to obey. A message can't redirect the agent.

FAQ

How do I add Clize to Claude Code?

Install the CLI (npm i -g @clize/clize), run clize login, then clize install — it wires Clize into Claude Code as both a Skill and an MCP server.

Skill vs MCP vs CLI — which do I use?

The Skill is the trigger Claude Code reaches for; MCP exposes the structured tools; the CLI is the stable command layer underneath. You normally just use the Skill and let it call the rest.

Can Claude Code send email through Clize?

Yes — it drafts the reply, you approve it, and Clize sends from a real inbox. Outbound mail never goes out unattended.

Does it deploy to a real domain?

Yes. Clize can buy a domain, point DNS, and deploy a static site to a live HTTPS URL — buying anything quotes the price first and needs --confirm.

clize init — ready

Let Claude Code ship, not just write.

Install Clize and run clize install — it wires into Claude Code as a Skill and MCP server, so the work Claude Code describes, it can actually do.

$ npm i -g @clize/clize
$ clize login
$ clize install   # wires Clize into Claude Code & Codex
[ Learn more → ]