Email tools for AI agents
It turns complex email into clean, agent-readable data. Connect your mailbox, import archives, export HTML, PDF, or Markdown, and let MailAtlas keep track of embedded images, attachments, metadata, and provenance.
python -m pip install mailatlas
Why MailAtlas
Email looks great in an inbox because it was designed for people. Give the same message to an agent as raw source or provider API output and it has to deal with MIME structure, rendered HTML, attachments, thread context, and provider-specific metadata.
Agents need structured, clean email access that does not pollute their context window. MailAtlas gives them an interface for reading email in the cleanest possible way, while preserving body content, HTML, attachments, embedded images, metadata, provenance, and the overall structure of each message.
.eml files, or mbox archives.How it works
Use the same workspace from the CLI, Python code, or MCP tools, depending on how your agent works.
Import from .eml files, mbox archives, Gmail, or selected
IMAP folders. Use whichever source matches where your email already lives.
MailAtlas gives agents clean body text, HTML, Markdown, PDF, JSON, attachments, embedded images, metadata, and links back to the original message.
When your agent needs to reply or follow up, MailAtlas sends through SMTP, Cloudflare Email Service, or Gmail API OAuth.
Sources and outputs
Connect a live mailbox and keep the agent's email workspace current with watch mode. You can also import archived email, export clean documents, and send through your existing provider from the same workspace.
sync Email files
Use file ingest when you already have individual .eml files, directories
of exported messages, or test fixtures.
.eml Mailbox archives
Use mbox ingest when you have a mailbox export on disk and want each
message stored as a document.
mbox Outbound email
Send email through a configured provider when your agent needs to reply, notify, or
follow up.
send Email workspace
MailAtlas stores clean email outputs as ordinary files and uses SQLite for lookup, dedupe, exports, provenance, mailbox sync state, and message records.
raw/ html/ store.db assets exports/ store.db .eml snapshots, body files, copied attachments, recipient metadata,
provider status, error details, and retry metadata.
outbound/ store.db MailAtlas receives from Gmail API or IMAP, including IMAP password or OAuth-token auth. For outbound email, it sends through SMTP, Cloudflare Email Service, or Gmail API OAuth.
Next steps
mailatlas doctor. install Import a sample email Import a local .eml file and inspect what MailAtlas stores. files Connect a mailbox Bring Gmail or selected IMAP folders into the same agent-readable inbox copy. imap Set up outbound email Send messages through your existing provider. send