Fluxmail

Fluxmail is self-hosted email infrastructure for agents and apps. It connects to Gmail, Microsoft 365, Outlook.com, and IMAP/SMTP mailboxes. Agents use MCP, apps and backend workflows use the versioned REST API, and operators use the CLI to connect mailboxes, manage access, and run the service.

Features

• 📬 Connect Gmail, Google Workspace, Microsoft 365, Outlook.com, and IMAP/SMTP mailboxes to one instance.
• 🤖 Give agents MCP tools to list, search, read, draft, reply, forward, send, schedule, and organize email.
• 🔌 Use the same mailbox operations from the versioned REST API and CLI.
• 🧵 Fetch complete messages and threads, work across several mailboxes, and download attachments.
• 🗂️ Mark mail as read, star or archive it, move it between folders, send it to Trash, and manage Gmail labels or Outlook categories.
• 🔐 Limit each client to selected mailboxes and actions with permission profiles or custom policies.
• 👥 Add members and choose which mailboxes each can access on Business and Enterprise plans.
• 🏠 Run Fluxmail locally or in Docker while keeping its database and encrypted provider credentials on your infrastructure.

Get started

Fluxmail requires Node.js 20.20.x, or Node.js 22.22 or later.

npm install -g fluxmail
fluxmail setup --name "Your name" --email you@example.com

Then follow the quickstart to connect a mailbox and choose how you want to use Fluxmail: MCP, REST API, or CLI.

For a local MCP connection, configure your client to launch fluxmail with arguments ["stdio", "--profile", "read-only"]. The client must run as the same operating-system user and use the same Fluxmail data directory as setup. Stdio uses the local member session; it does not need an API key or a separate HTTP server. Ask the client to call list_accounts to check the connection. A fresh instance returns an empty account list.

See Connect an MCP client for client configuration and HTTP connections. Its Cline section covers MCP settings and Cline CLI setup, also available as llms-install.md in this repository.

Documentation

• Overview
• MCP tools
• Build with REST
• REST API
• Permissions
• Configuration
• CLI reference
• Gmail setup
• Outlook setup
• IMAP setup
• Architecture
• Teams and plans
• Authentication and instances

Plans and license

The Personal plan supports three mailboxes and one member. Paid plans raise those limits for teams that share an instance. See Fluxmail pricing for current details.

Fluxmail is source available under the Elastic License 2.0. You may use, modify, create derivative works, and redistribute Fluxmail subject to that license. Running a fork does not by itself require a paid Fluxmail subscription, and the built-in Personal plan supports three mailboxes and one member without a paid key.

Official Pro, Business, and Enterprise entitlements require a valid Fluxmail license key. ELv2 does not allow you to change or circumvent license key functionality, remove protected functionality, or provide Fluxmail itself as a hosted or managed service that exposes a substantial set of its features. Use of the Fluxmail name and logos is also subject to the Fluxmail Terms of Service.