Skip to main content
Glama
fluxmailai

Fluxmail

by fluxmailai
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.
    28 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
    -

  • Postroom

    vaclav-kozak
    A
    license
    Not graded
    quality
    A
    maintenance
    A self-hosted remote MCP server that gives AI assistants read, organize and optional send access to mail, calendars, tasks and contacts across many IMAP, Gmail, CalDAV, CardDAV and Google accounts behind one authenticated endpoint.
    1
    Apache 2.0
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

B3.3/5.0

Scored across 23 tools

Disambiguation4/5

Most tools target distinct resources or actions, with clear boundaries between accounts, folders, messages, drafts, sends, and schedules. The main overlaps are list_emails vs. search_emails vs. search_emails_batch, and get_email vs. get_email_body vs. get_thread, though descriptions mostly clarify account scope, query syntax, and body bounds.

Naming Consistency5/5

Tools consistently use snake_case with a predictable verb_noun or verb_noun_qualifier pattern. Names like get_draft, list_emails, create_draft, send_email, and cancel_scheduled_email are easy to parse and follow the same convention throughout.

Tool Count3/5

At 23 tools, the surface is heavy for an email integration, sitting in the borderline 16-25 range. The domain is broad enough to justify many tools, but some could likely be consolidated without losing capability.

Completeness4/5

Core email workflows are well covered: account listing, folder/label discovery, listing/searching/reading messages, drafts, sending, forwarding, attachments, scheduling, and delivery status. Minor gaps include explicit folder/label management and direct delete/archive operations, though modify_emails may cover some of these through provider-supported actions.

Maintenance

ActivityActive
ResponsivenessWithin a week

Resources