Self-hosted email infrastructure for agents and apps

Build apps and agent workflows on top of Gmail, Outlook, or IMAP. Connect through MCP, REST API, or CLI.

Claude
ChatGPT
Codex
OpenClaw
Hermes
Cursor
Claude Code v2.1.201
Fluxmail MCP · local stdio
>

One email engine, three interfaces

Each interface works with the same email operations, mailboxes, and access controls.

MCP

Give Claude Code, Codex, Hermes, or any other agent access to your email.

  • Triage your inbox and prepare a morning brief
  • Search for a message or attachment in natural language
  • Draft replies for review, then send with approval
Connect an MCP client

REST API

Use one unified API across providers to build your app on top of Fluxmail.

  • Add a shared inbox to a support or operations tool
  • Route receipts and attachments into existing systems
  • Create, send, or schedule mail from a backend workflow
Explore the REST API

CLI

Read and manage email from your terminal.

  • Connect Gmail, Outlook, and IMAP accounts
  • Search, draft, send, and interact with your mail via CLI commands
  • Run the MCP server via stdio or Streamable HTTP
Browse CLI commands

Connect with any email provider

Connect Gmail, Google Workspace, Outlook, Exchange, or any mailbox with IMAP/SMTP access.

Fluxmail

Email infrastructure for agents and apps

MCP

REST API

CLI

Gmail

Outlook

IMAP / SMTP

Your emails are private and secure

Fluxmail runs on your own infrastructure.

Run on your own infra

You run the MCP server on your own infrastructure and have full control over how it works.

Your emails are private

Your agent connects to your email provider through the server you run. Your emails are not stored on our servers.

Source-available code

The code is public on GitHub. You can audit it, report issues, and follow along on progress.

Frequently asked questions

Still have questions? Email us or read the quickstart.

Build on top of email

Run Fluxmail on your own infrastructure and use it through MCP, REST API, or CLI.