Fluxmail Cloud

ai.fluxmailPublished by fluxmail.aiOfficial publisherv0.1.0Updated Oct 24, 2026

Hosted MCP server for your Gmail, Outlook and IMAP mail, with mailboxes and scopes set per agent.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

A hosted MCP server that gives an assistant access to your Gmail, Outlook and IMAP mail, with mailboxes and scopes set per agent.

What you can do
Fluxmail Cloud is a remote, hosted MCP server for email. According to its registry entry, it connects an assistant to Gmail, Outlook and IMAP mail accounts, and lets you choose which mailboxes and which scopes each agent may use. No tool list is published, so the exact operations available are not documented in the supplied material.
When to use it
Consider it when you want an assistant to work with your email through a hosted service rather than a locally installed package, and when you need per-agent limits on which mailboxes and permissions it can reach.
Requirements
A remote MCP endpoint at cloud.fluxmail.ai over streamable HTTP. OAuth authentication is required. No environment variables, headers or packages are declared. It is not desktop-only and can run in a web context.
Before you install
It asks for OAuth access to your email accounts, so review the scopes and mailboxes granted to each agent before connecting. The published description does not state whether the server can send, modify or delete messages, or what data leaves your mail provider; confirm this before use.

Installation

In SourceWeft

  1. Open Fluxmail Cloud in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.fluxmail%2Fcloud/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "fluxmail-cloud": {
      "type": "http",
      "url": "https://cloud.fluxmail.ai/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestOct 23, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Fluxmail integrations