Skip to main content
Glama
churichard

Fluxmail

by churichard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Fluxmail

Related Servers

  • mcp-email

    OneShotForge
    F
    license
    Not graded
    quality
    D
    maintenance
    Self-hosted MCP server for any IMAP/SMTP inbox. Multi-account in one config. Built for Claude Code.
    -

  • mcp-email

    algonacci
    A
    license
    Not graded
    quality
    C
    maintenance
    A minimal MCP server for reading, searching, managing, and sending email over IMAP and SMTP.
    MIT

  • email-mcp

    dengjianbo3
    A
    license
    Not graded
    quality
    B
    maintenance
    A self-hosted MCP server for Gmail and Outlook that lets MCP clients read, search, send, reply, and manage email via OAuth, with no built-in secrets and support for both stdio and HTTP transports.
    19 npm
    ISC

  • outlook-mcp-server

    dhtim135
    F
    license
    A
    quality
    D
    maintenance
    A lightweight MCP server for personal Microsoft Outlook/Hotmail accounts, enabling email search, reading, attachment management, and folder operations via Microsoft Graph API with OAuth device-code flow.
    6
    1
    -

  • mcp-imap

    TheGoldfingerCH
    F
    license
    Not graded
    quality
    D
    maintenance
    A minimal MCP server for reading and sending emails via IMAP/SMTP, supporting multiple accounts in a single instance with zero external dependencies.
    1
    -

  • mcp-gmail-oauth

    flujo-app
    A
    license
    Not graded
    quality
    C
    maintenance
    A self-hostable Gmail MCP server that enables Gmail search/read, sending, replies, drafts, labels, and attachment downloads via MCP tools with OAuth authorization. Supports stdio and streamable HTTP transports.
    1
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 19 tools

Disambiguation4/5

Most tools target distinct resources and actions: list_emails is for browsing, search_emails is for query syntax, and get_email/get_thread retrieve full content. The only mild ambiguity is between list_emails and search_emails since both can filter by conditions, but their descriptions clarify the intended use.

Naming Consistency5/5

Every tool follows the same snake_case verb_noun pattern (list_accounts, get_email, create_draft, cancel_scheduled_email, download_attachment). Names are predictable and map clearly to their operations.

Tool Count4/5

19 tools is slightly above the typical 3-15 sweet spot, but each tool covers a distinct email operation and the count is appropriate for the domain. There is no obvious filler or redundancy.

Completeness5/5

The tool surface covers the full email lifecycle: browsing, searching, reading, drafting, sending, scheduling, forwarding, modifying, and attachments. It also handles account-level introspection and failure recovery via get_status, so agents have no dead-end workflows.

Maintenance

ActivityActive
ResponsivenessNo issues

Resources