Overview

EmailFS receives inbound email for your domains, normalises each message to Markdown, stores threads as folder-like paths in R2, and exposes the result over a REST API and an MCP server. There is no IMAP, no MIME parsing in your code, and no OAuth flow for your agents to deal with.

The stack is entirely Cloudflare-native:

  • Haraka SMTP → POST /v1/inbound → Cloudflare Worker
  • Worker parses with PostalMime, stores body as Markdown in R2, meta in D1
  • REST API and MCP server run on the same Worker at api.emailfs.com
The base API URL is https://api.emailfs.com. All endpoints require a Bearer token.