fluxmail.ai valid

Fluxmail

Connect ChatGPT, Claude, and other agents to Gmail, Outlook, or IMAP over MCP. Agents can search, read, draft, and send email with the permissions you approve.

For agents: Fluxmail connects AI agents to Gmail, Outlook and IMAP over MCP, REST or CLI, with permission controls; self-hosted with docs on auth, backup and REST keys.

mcp servergmail apiemail for agentsself-hostedrest api

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T08:27:51.334Z. Cached copy · Source on fluxmail.ai

# Fluxmail

> Connect ChatGPT, Claude, and other agents to Gmail, Outlook, or IMAP over MCP. Agents can search, read, draft, and send email with the permissions you approve.

Fluxmail gives AI agents and apps access to Gmail, Outlook, and IMAP mailboxes. It comes in two forms that share the same email operations and permission model: Fluxmail Cloud, a hosted service, and Fluxmail Self-Hosted, which you run on your own computer or server. The home page compares them.

Fluxmail Self-Hosted, described at /self-hosted, connects Gmail, Outlook, Exchange, and IMAP mailboxes through MCP, a versioned REST API, and a CLI. All three interfaces can search, read, draft, send, schedule, and organize email. AI agents can connect over local stdio or Streamable HTTP, while apps and backend workflows can use REST. The CLI includes Fluxmail-managed Gmail OAuth and also accepts custom Google credentials. Fluxmail encrypts provider credentials in local storage. Installation instructions are available at /docs/quickstart.

Fluxmail Desktop is a free, open-source email client for macOS with public releases on GitHub, linked from /desktop. It runs the Fluxmail engine inside the app and connects directly to Gmail, Outlook, and IMAP providers, with no Fluxmail server in between. It shares connected accounts with the Fluxmail CLI and MCP server, so people and agents can work with the same mailboxes.

Fluxmail Cloud provides hosted MCP and REST access to existing mailboxes at cloud.fluxmail.ai. Cloud uses separate mailbox connections, OAuth authorization for MCP clients, and scoped agent keys for REST automation. Cloud documentation is at /docs/cloud, with a pasteable agent setup prompt at /docs/cloud/quickstart#agent-first-setup and a Cloud-only plain-text guide at /docs/cloud/llms.txt. Cloud offers Pro and Business subscriptions, a seven-day trial on a workspace's first subscription, and workspace invitations on Business. Cloud scheduling and remote CLI configuration are not implemented.

## Key facts

- Self-hosted server: Fluxmail packages its CLI, MCP server, and REST API in the `fluxmail` npm package (Node.js 20.20.x or 22.22+) and a Docker image, with source available on GitHub.
- Self-hosted transports: `fluxmail stdio` connects local agents (Claude Code, Claude Desktop, Cursor, Codex, Gemini CLI, VS Code Copilot); `fluxmail serve` runs a Streamable HTTP MCP endpoint authenticated with `fmk_` API keys.
- Self-hosted email operations: MCP, REST API, and CLI can read and search threads, manage drafts, send and forward email, organize messages, and handle attachments.
- Gmail OAuth: the Fluxmail CLI includes a managed OAuth flow and a bundled local OAuth client, and it also accepts custom Google credentials.
- Self-hosted privacy: Google and Microsoft OAuth tokens and IMAP/SMTP passwords are stored locally in SQLite and encrypted with AES-256-GCM, with no Fluxmail cloud involved.
- Self-hosted providers: Gmail, Google Workspace, Outlook, Exchange, and mailboxes with I
…

Related sites

Other listed sites in AI agents and MCP. See the whole category →

Machine-readable: GET /v1/resolve?q=fluxmail.ai · GET /v1/domain/fluxmail.ai · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for fluxmail.ai:
1. POST https://agentwebmap.com/v1/sites/fluxmail.ai/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://fluxmail.ai/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/fluxmail.ai/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/fluxmail.ai).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.