Fluxmail Cloud is available today. It's a hosted version of Fluxmail that connects ChatGPT, Claude, Codex, Cursor, and other MCP clients to your Gmail, Outlook, or IMAP mailbox. You don't need to install anything or keep a server running.
Fluxmail MCP, which we released in July, runs on your own machine or server. A local install works well for a coding agent on your laptop. It doesn't help when you want to use ChatGPT or Claude on the web, or when an agent runs somewhere your machine can't reach. Cloud runs the server for you at cloud.fluxmail.ai, and any client that supports remote MCP with OAuth can connect to it.
Set it up from your agent
Paste this prompt into a coding agent:
Set up Fluxmail Cloud. Read https://fluxmail.ai/docs/cloud/setup.txt and follow the setup guide. Configure the connection, let me choose mailboxes and permissions in Fluxmail, and verify it works. Guide me through any sign-in or consent steps.
The agent reads the setup guide and adds the Fluxmail Cloud server to its client configuration. Then it sends you to sign in. You create an account, start a trial, and connect a mailbox. Gmail and Outlook use their own sign-in pages. For other providers you enter IMAP and SMTP settings, which the dashboard fills in for iCloud, Yahoo, AOL, and Fastmail.
After you approve the agent, it checks the connection by listing your five most recent emails without opening their bodies.
If you'd rather configure the client yourself, the MCP setup guide has instructions for ChatGPT, Claude, Claude Code, Codex, Cursor, Hermes, and Muse.
Each agent gets its own permissions
When an agent connects, Fluxmail shows you a consent page listing the mailboxes and permissions the agent requested. You pick the workspace and mailboxes it can use, and you can uncheck any of the requested permissions before you approve.
There are six permissions:
- Read emails
- Manage drafts
- Organize emails (flags, labels, archive, and move)
- Move to and from Trash
- Permanently delete emails
- Send emails
Three presets cover common setups: Read only, Read and write (everything except sending), and Full mail access. Permanent deletion is never included in a preset, so you have to select it yourself.
Every client you approve gets a separate connection, and you can review or revoke each one from the dashboard without affecting the others. Access tokens last 15 minutes and clients refresh them automatically. If a client goes 30 days without refreshing, it has to sign in again, and every approval expires after 90 days. How permissions work covers the details.
REST for scripts and apps
For scripts and apps that don't use MCP, Cloud also has a REST API at https://cloud.fluxmail.ai/api/mail/{operation} that uses the same operations and permission scopes. You create a named agent key in the dashboard, pick its mailboxes and scopes, and set an expiry from 7 days to a year, or no expiry at all.
Sends work the same way over MCP and REST. Each send takes an idempotency key, so if a request times out you can look up whether the message went out instead of sending it twice. Sending and retries explains how to handle uncertain outcomes.
What Cloud stores
Cloud stores encrypted provider credentials, account details, token records, and send records. It doesn't keep a copy of your mail. On every request it checks the connection's mailboxes and permissions, then calls Gmail, Outlook, or your IMAP server directly. Disconnecting a mailbox or deleting your account leaves your mail at the provider untouched.
Pricing
Cloud has two plans, and both start with a 7-day free trial:
- Pro is $15 a month, or $120 a year, for one person with up to 10 mailboxes.
- Business is $25 per member each month, or $240 per member a year, for teams of up to 100. Each member adds 20 mailboxes to a shared pool, and the workspace owner can invite members.
See pricing for the full comparison.
Cloud and self-hosted
Fluxmail Self-Hosted is still available and still free for up to three mailboxes. It uses the same permission model. Self-host if you want everything on your own hardware or need scheduled sends, which Cloud doesn't support yet. Choose Cloud if you'd rather not run a server, or if your agent runs in a browser or on someone else's infrastructure.