Skip to main content
Glama
Sign In
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
    D
    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.
    18 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.
    2
    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.2/5.0

Scored across 33 tools

Disambiguation4/5

Most tools target a clearly distinct resource+action (drafts CRUD, star/unstar, trash/restore, scheduling vs sending), and move_emails explicitly excludes archive/trash, which removes a common confusion. The main overlap is list_emails, which is described as able to 'list or search' and filter by sender/date/read state, versus search_emails/search_emails_batch with typed query syntax; get_email, get_email_body and get_thread also blur slightly around reading message bodies.

Naming Consistency5/5

Every tool is snake_case with a leading verb (list_, get_, create_, update_, delete_, send_, search_, mark_, add_/remove_, archive_/trash_/restore_), and the noun is the resource being acted on. Paired operations are named symmetrically (mark_emails_read/mark_emails_unread, star_emails/unstar_emails, add_labels/remove_labels), making the pattern highly predictable.

Tool Count2/5

At 33 tools the surface is heavy for an email server, and several pairs could be collapsed into one tool with a state flag (mark read/unread, star/unstar, add/remove labels). The list/search/body-reading split also adds tools that duplicate capability rather than adding new scope.

Completeness4/5

Coverage is strong across the lifecycle: multi-account listing, folders/labels, search (single and batch), body pagination, threads, full draft CRUD, send/preview/reply/forward/schedule, delivery status, and bulk message state operations. Gaps are minor: no permanent delete/empty-trash, and no folder or label creation/management tools, but agents can work around these.

Maintenance

ActivityActive
ResponsivenessWithin a week

Resources