Agentic Inbox

Cloudflare publishes Agentic Inbox as a mail client that runs in your own Cloudflare account. Email Routing delivers incoming mail, each mailbox keeps its own Durable Object with SQLite storage, and R2 holds attachments. The agent runs on the Agents SDK and Workers AI.

The React interface has a rich text composer, threaded reply and forward, folders, search and attachments. A side panel holds the Email Agent, which uses the @cf/moonshotai/kimi-k2.5 model and has nine tools for reading, searching, drafting and sending mail. When new mail arrives, the agent can read it and prepare a draft reply automatically. Each mailbox can carry its own system prompt, and chat history persists. An MCP endpoint at /mcp gives external tools such as Claude Code or Cursor access to the same mailboxes. A Hono Worker serves the API and the server-rendered app. Outbound mail leaves through Email Service via the send_email binding. Cloudflare Access is the only authentication layer, and the Worker refuses production traffic until Access is configured. The Deploy to Cloudflare button provisions R2, the Durable Objects and Workers AI, and asks for a DOMAINS value. You then turn on one-click Cloudflare Access for the Worker and save its POLICY_AUD and TEAM_DOMAIN values as secrets. Next, you add an Email Routing catch-all rule that forwards to the Worker and enable Email Service for outbound mail. Finally, you create the first mailbox in the app.

Built for: Developers and small teams with a domain on Cloudflare who want a private web inbox and an AI assistant for drafting replies.

What you can use it for

• Run a self-hosted web inbox for a custom domain
• Review AI-drafted replies before anything is sent
• Keep separate hello@ and support@ mailboxes on one domain
• Search and draft mail from Claude Code, Cursor or another MCP client

Deploy

• One-click · main path

  Branch main, requires Workers Paid

  Deploy to Cloudflare

• CLI

  Branch main, requires Workers Paid

  Set DOMAINS in wrangler.jsonc first. POLICY_AUD and TEAM_DOMAIN come from the Cloudflare Access modal after the first deploy.

  npm install
  npx wrangler r2 bucket create agentic-inbox
  npm run deploy
  npx wrangler secret put POLICY_AUD
  npx wrangler secret put TEAM_DOMAIN

  Copy
  Docs

After the button deploy, you set up Cloudflare Access with two secrets, an Email Routing catch-all rule and Email Service by hand.

What it needs to run

• Workers AIAI
• Durable ObjectsEmailAgent, EmailMCP, MailboxDO
• R2 bucketsagentic-inbox
• Email sendingEMAIL

Good to know

There is no per-mailbox authorization: anyone who passes the shared Cloudflare Access policy can open every mailbox, including through the /mcp endpoint. Nothing has been merged since April 2026, and community pull requests are waiting for review. An open issue reports that auto-drafting fails with HTTP 500 for mailboxes never opened in the UI.

Cost on Cloudflare

Where this comes from

• Repositoryhttps://github.com/cloudflare/agentic-inbox
• Documentationhttps://developers.cloudflare.com/email-routing/email-workers/send-email-workers/

An alternative to Gmail.