Install MailAtlas
Install MailAtlas before running the Quickstart, syncing an IMAP folder, exporting documents, or sending outbound email.
The recommended path is a Python virtual environment and PyPI. Use uv, Homebrew, or a source checkout only if those match your local workflow.
MailAtlas is currently alpha. Expect CLI, schema, and packaging details to keep improving.
Requirements
Section titled “Requirements”- Python 3.12 is recommended. The package metadata currently allows Python 3.11 and newer.
- A local directory where MailAtlas can create a workspace.
- Chrome or Chromium only if you want PDF export.
- Provider credentials only if you plan to receive from IMAP or send outbound email.
The core file-ingest path does not require a hosted MailAtlas service, an email provider account, or a cloud service.
Install with pip
Section titled “Install with pip”python3.12 -m venv .venvsource .venv/bin/activatepython -m pip install mailatlasmailatlas doctormailatlas doctor creates a temporary store, ingests a synthetic message, and verifies basic storage and JSON export. If Chrome or Chromium is available, it also checks PDF export. If the browser is missing, the doctor command warns instead of failing unless PDF is explicitly required.
Optional extras
Section titled “Optional extras”Use extras only when you need them:
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.
Configure a workspace root
Section titled “Configure a workspace root”MailAtlas stores data in one workspace root. By default, the root is .mailatlas in the current directory.
export MAILATLAS_HOME="$PWD/.mailatlas"You can also pass a root per command:
mailatlas --root .mailatlas listThe workspace root contains local files and store.db. It can include raw email, HTML snapshots, extracted assets, exports, outbound records, and SQLite metadata.
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 Quickstart if your email is already on disk as
.emlfiles. - Use Mbox Ingest if you have a mailbox archive on disk.
- Use IMAP Receive if MailAtlas should connect to a live mailbox.
- Use Outbound Email if your application needs send records and provider delivery.