Our take
- Activity
- 19
- Community
- 4
- Issues
- 46
- Pull requests
- 20
+423 stars in the last 30 days
- Fewer contributors than 91% of the projects we track
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
8,788Forks
1,158Change since Nov 17, 2026: +8 stars·0 forks
Overview
Agentic Inbox combines a web-based email client with an AI assistant that can read messages, search conversations, and prepare replies. It runs on Cloudflare Workers, using Durable Objects for isolated mailbox storage and R2 for attachments.
It is aimed at people who want to manage email through their own Cloudflare account and connect AI tools to inbox workflows. It is not designed for separate access controls per mailbox: anyone admitted by the shared Cloudflare Access policy can access all mailboxes.
Key Features
- Send and receive email through Cloudflare Email Routing and Email Service.
- Organize messages with folders, search, threaded replies and forwards, and attachments.
- Store each mailbox in its own Durable Object with a SQLite database, with attachments in R2.
- Use an AI agent to read, search, draft, and send email through nine email tools.
- Generate draft replies when new email arrives, with explicit confirmation required before sending.
- Configure per-mailbox system prompts and retain chat history.
- Connect external AI tools to the MCP server at
/mcp.
Use Cases
- Individuals or small teams already using Cloudflare who want a self-hosted email interface on their own account.
- Users who want an AI assistant to find messages or prepare replies while keeping final send approval in their hands.
- Developers exploring email workflows that connect Cloudflare Workers, Workers AI, and the Agents SDK.
- People who want external MCP-compatible AI tools to work with their inbox, provided they accept shared access across all mailboxes.
Getting Started
npm install
npm run dev
See the repository README for configuration, deployment, and setup details.
Considerations
- A Cloudflare account and domain are required, along with Email Routing, Email Service, and Workers AI for the corresponding features.
- Cloudflare Access is required in deployed or shared environments. It is the sole authorization boundary: an allowed user can access every mailbox, including through MCP.
- Deployment requires additional setup after using the deploy flow, including Access secrets and Email Routing configuration. Follow the README's deployment guide before exposing the app.
- The AI agent can draft and send messages, so review its actions; sending requires explicit confirmation in the described auto-draft flow.
Found this useful?
Share it with someone who would like agentic-inbox.