Post
124
I built inboxmcp, a hosted MCP server that gives your own agent (Grok Bot, Claude, any remote-MCP client) read-only access to the IMAP inboxes you choose.
A few design choices that might interest MCP builders:
- Email content is returned as untrusted data, kept separate from the owner's saved instructions
- OAuth + PKCE with per-mailbox grants instead of passwords
- Each AI connection keeps its own server-side checkpoint (claim_email_batch / complete_email_batch), so scheduled agents resume without Notion pages or state files
Design notes: https://huggingface.co/blog/dylantom2012/inboxmcp-agent-email-mcp
Endpoint: https://app.inboxmcp.ai/mcp (MCP Registry: io.github.zhlei07/inboxmcp)
Feedback on the batch/lease design is very welcome. (I'm the maker.)
A few design choices that might interest MCP builders:
- Email content is returned as untrusted data, kept separate from the owner's saved instructions
- OAuth + PKCE with per-mailbox grants instead of passwords
- Each AI connection keeps its own server-side checkpoint (claim_email_batch / complete_email_batch), so scheduled agents resume without Notion pages or state files
Design notes: https://huggingface.co/blog/dylantom2012/inboxmcp-agent-email-mcp
Endpoint: https://app.inboxmcp.ai/mcp (MCP Registry: io.github.zhlei07/inboxmcp)
Feedback on the batch/lease design is very welcome. (I'm the maker.)