Install MailAtlas
Install MailAtlas from PyPI to use the CLI, Python API, or MCP server locally.
This page shows the pip, uv, Homebrew, and source install paths. Start with pip unless you prefer one of the other tools.
MailAtlas is currently alpha. Expect CLI, schema, and packaging details to keep improving.
Requirements
Section titled “Requirements”- Python 3.12 is recommended.
- A local directory where MailAtlas can write an email workspace.
- Chrome or Chromium only if you want PDF export.
- Provider credentials only when you connect a live mailbox or send email.
MailAtlas does not require a hosted MailAtlas service. For live mailboxes or sending, it uses the provider credentials you configure for IMAP, Gmail OAuth, SMTP, Cloudflare, or Gmail sending.
Install with pip
Section titled “Install with pip”python3.12 -m venv .venvsource .venv/bin/activatepython -m pip install mailatlasVerify the installation:
mailatlas doctormailatlas doctor verifies that MailAtlas can create a temporary workspace, ingest a sample message, read it back, and export JSON. PDF export is checked only when Chrome or Chromium is available.
Optional extras
Section titled “Optional extras”python -m pip install "mailatlas[mcp]"python -m pip install "mailatlas[keychain]"Use mailatlas[mcp] when you want to run the optional MCP server.
Use mailatlas[keychain] when you want the local Gmail OAuth helper to store token material in the operating system keychain.
The Python API ships in the base package.
Set the email workspace directory
Section titled “Set the email workspace directory”MailAtlas writes received messages, sent messages, exports, assets, and SQLite lookup data into a local email workspace. By default, the workspace is .mailatlas in the current directory.
export MAILATLAS_HOME="$PWD/.mailatlas"You can also pass a root per command:
mailatlas --root .mailatlas listUse MAILATLAS_HOME when you want several commands to share the same workspace. Use --root when you want a one-off command to point somewhere else.
Optional PDF export setup
Section titled “Optional PDF export setup”PDF export uses local Chrome or Chromium. Install a browser if you need PDF exports.
If the browser executable is not on the default path, set:
export MAILATLAS_PDF_BROWSER="/path/to/chrome-or-chromium"Install with uv
Section titled “Install with uv”python3.12 -m pip install uvuv tool install mailatlasmailatlas doctorInstall with Homebrew
Section titled “Install with Homebrew”brew tap mailatlas/mailatlasbrew install mailatlasmailatlas doctorIf Homebrew resolves a different formula named mailatlas, use:
brew install mailatlas/mailatlas/mailatlasInstall from source
Section titled “Install from source”Use a source checkout when you want shipped fixtures, examples, the demo API, or editable development.
git clone https://github.com/mailatlas/mailatlas.gitcd mailatlaspython3.12 -m venv .venvsource .venv/bin/activatemake bootstrap-pythonmailatlas doctorIf you are changing the docs site too:
make bootstrap-docsRun the local command list:
make helpNext step
Section titled “Next step”- Use Manual IMAP Sync when your agent should read a live mailbox.
- Use Gmail Receive when your agent should read Gmail with OAuth.
- Use Quickstart when you want to try local
.emlfiles. - Use Python API when you want to embed MailAtlas in an application or worker.
- Use MCP Server when you want to expose email tools to an AI agent.
- Use Outbound Email when your agent or application needs to send through a configured provider.