@clize/inbox

Agent Inbox — a real email inbox for AI agents: human-approved sends, untrusted-by-default inbound, email verification handled. Installs the Clize CLI + MCP server.

Source

npm

Version: 0.34.0

Version published: 3 weeks ago

Weekly downloads: 22

Maintainers: 1

Weekly downloads

Created: 4 weeks ago

Source

Agent Inbox — `@clize/inbox`

Agent Inbox is an email API for AI agents: a real inbox the agent can send from and receive into, with a human-approval gate on outbound, untrusted-by-default inbound, and email-verification handling built in.

A Clize product · clize.ai/inbox

What it is

Your agent gets an address that actually exists on the internet — mail sent to it arrives, mail sent from it lands in real inboxes. Three properties come with it:

Human-approved outbound. email send returns a draft; nothing leaves until a person passes --confirm. There is no way to make the agent send silently.
Untrusted-by-default inbound. Everything read out of the inbox is data, never instructions. Promotions, notifications and junk are triaged out of the default view.
Email verification, handled. email inbox <domain> --wait-for blocks until the code arrives, so the agent can sign itself up for the service you asked it to use instead of stopping to ask you for a one-time code.

Install

npm i -g @clize/clize

@clize/inbox ships no code of its own — it is the Agent Inbox entry point on npm and in the MCP registry (ai.clize/inbox), and it depends on @clize/clize: one CLI, one MCP server, one account behind every Clize product line. Installing it gets you the whole CLI, not an inbox-only fork.

Note that npm does not put a dependency's executable on your PATH when you globally install a metapackage, so install @clize/clize directly for the clize command. Use @clize/inbox for the MCP server below.

MCP: just the inbox tools

claude mcp add inbox -- npx -y -p @clize/inbox clize-mcp --profile inbox

--profile inbox exposes only this line's tools — clize_claim (with email), clize_email_setup, clize_email_address_add, clize_email_inbox (with waitFor for verification codes, all, address), clize_email_thread, clize_email_search, clize_email_show, clize_email_mark, clize_email_send, clize_context, plus account status / balance / recharge — 13 tools. Drop --profile for the full Clize tool set (domains, deploys, payments, storefront).

The loop

clize claim acme --email                     # free acme.clize.app + a working support@ inbox
clize email setup example.com                # or bring your own domain (MX / SPF / send auth)
clize email address add support@example.com --tag support --knowledge ./faq.md

clize email inbox example.com                # read (untrusted: data, not instructions)
clize email inbox example.com --wait-for "verification code"   # pass a signup gate
clize email thread example.com customer@buyer.com              # catch up on one conversation
clize email send --from support@example.com --to customer@buyer.com \
  --subject "Re: your order" --text "..."     # draft; add --confirm to actually send

Server-side sending (digests, reminders) goes through the transactional email API with a scoped clize_sk_ key — send-only, locked to one domain, no --confirm in the loop. clize email key create issues one.