ONE INSTALLATION. YOUR DOMAINS.

Send from your app.
Read the replies.

Send application mail, read incoming messages, and connect your agents without moving the installation out of your Cloudflare account.

FEATURE DETAILS

A closer look.

Choose the parts your application needs.

A browser inbox for your domains’ mail

Threads, labels, search, attachments, compose, scheduled sends, spam controls, and a Sent view. Successful developer API sends also get mailbox copies. Outbound mail uses Cloudflare Email Service, which Cloudflare’s terms cover for transactional sending; confirm with Cloudflare before relying on it for everyday conversational replies. You can add domains after setup, review their DNS, and create personal, role, agent, or disposable addresses.

Transactional email for applications

Use domain-scoped API keys, idempotent requests, reusable templates, delivery timelines, suppressions, and signed webhooks. Optional open and click tracking starts off. Logs show individual message events; Box Ox does not include an aggregate mail-performance dashboard.

Agent access with boundaries

The remote MCP endpoint runs on your Worker. OAuth approval, mailbox grants, sending caps, and revocation control what each agent can do. The downloadable CLI and email skill help agents integrate your applications. Mail MCP access does not grant Cloudflare account administration.

Processing stays your choice

Local filters, reputation checks, and AI are separate settings. AI remains off until you choose it. External providers receive selected content when enabled. Read the data-flow details.

Box Ox holding an envelope

Start building with Box Ox today.

Your app’s mail. Its replies. Your Cloudflare.

Get your own Box OxSelf-hosted · Free software · Cloudflare bills your usage, and R2 needs a payment method on file