How do I add an MCP server to Claude Code?

Install Clize (npm i -g @clize/clize), run clize login, then clize install --mcp. It registers Clize as a Claude Code MCP server (and a Skill). The manual equivalent is claude mcp add clize -- clize-mcp.

How do I verify the MCP server is connected to Claude Code?

Run claude mcp list. Clize should appear among the registered MCP servers. Start a new Claude Code session and the clize tools — domains, email, deploy, status — become callable.

What is the difference between the Clize Skill and MCP server in Claude Code?

clize install adds a Skill by default — the trigger layer Claude Code reaches for, with the safety rules. Adding --mcp also registers the MCP server, the structured tool layer Claude Code discovers automatically. Most setups use both.

Can Claude Code handle support email once connected?

Yes. Tag a support@ inbox at your docs and Claude Code can read an incoming message, draft a reply from your docs, wait for your approval, and send — then resume the thread next session.

Add Clize MCP server to Claude Code (step by step)

A four-step guide to adding Clize as a Claude Code MCP server — so Claude Code can act outside the sandbox: domains, inboxes, deploys, and support. For the overview, see Claude Code MCP server.

Before you start

You need Node.js (for the npm install) and Claude Code already installed. Clize is the capability layer — it needs no model API key of its own.

1. Install Clize and log in

Install the CLI globally, then authenticate. Login uses Clize's hosted layer, so there are no keys to paste.

$ npm i -g @clize/clize
$ clize login

2. Add Clize as a Claude Code MCP server

One command wires Clize into Claude Code as both a Skill and an MCP server. The --mcp flag is what registers the structured tool layer (without it, Clize installs only as a Skill).

$ clize install --claude --mcp

Prefer to configure it by hand? That's the exact registration the installer runs:

$ claude mcp add clize -- clize-mcp

3. Verify the connection

Ask Claude Code which MCP servers it knows about. Clize should be listed.

$ claude mcp list

Start a new Claude Code session and the Clize tools — domains, email, deploy, status — are callable. The Skill is the trigger layer; the MCP server is the structured tool layer; the same actions also run as a stable CLI.

4. Set up a support inbox

The most common first workflow: tag a support@ inbox, point it at your docs, and run the loop — Claude Code reads an incoming message, drafts a reply from your docs, you approve, it sends, and it picks the thread back up next session. Full walk-through in AI customer support agent. To ship a site instead, see AI agent deployment.

The safety gates

Because these are real actions, 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.

Add Clize MCP server to Claude Code