Skip to main content
Glama
pp123ys

email-mcp-server

by pp123ys
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to email-mcp-server

No user-submitted related servers found.

    Related Servers

    • anymail-mcp

      DeamonDev888
      A
      license
      Not graded
      quality
      B
      maintenance
      Connects any IMAP/SMTP mailbox to AI agents via MCP, enabling email read, search, send, reply, and management through natural language.
      8 npm
      MIT

    • simple-email-mcp

      mexican75
      A
      license
      B
      quality
      B
      maintenance
      Enables users to manage email accounts via IMAP/SMTP, including reading, searching, sending emails with attachments and calendar invites, all through natural language interactions with MCP-compatible clients.
      1
      4
      MIT

    • mcp-imap-smtp

      ragavtech
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects MCP-compatible AI assistants to any IMAP/SMTP mailbox, enabling email search, reading, folder management, and sending with automatic saving to Sent.
      1
      MIT

    • Mailoo

      Bitfloo
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to read, search, send, manage, schedule, and analyze emails across multiple IMAP/SMTP accounts via MCP, with features like OAuth2, calendar extraction, analytics, and real-time email watching.
      470 npm
      LGPL 3.0
    • InboxAPI CLI by inboxapi

      InboxAPI CLIofficial

      inboxapi
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides an AI agent with its own email address to send, receive, and manage emails via MCP. No email server setup required.
      38 npm
      12
      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

    B3.4/5.0

    Scored across 30 tools

    Disambiguation3/5

    Some tools overlap heavily: set_flag and pin_email both star/flag emails; archive and move_email both move emails (archive is a special case of move); manage_labels and create_label both handle labels. The email_id format is consistently documented but the overlapping actions create ambiguity.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern (list_inbox, read_email, send_email, save_draft, create_label). Minor deviations: manage_labels is verb_noun but generic, get_account_status/configure_account are consistent, but mix of get_ vs list_ and set_flag vs pin_email is slightly inconsistent.

    Tool Count3/5

    30 tools is on the heavy side for an email server, but the domain is broad (account config, send/receive, folders, labels, threads, attachments, flags). Still, several tools could be consolidated or removed.

    Completeness4/5

    The surface covers core email workflows well: reading, sending, drafting, replying, forwarding, searching, folders, attachments, threads, labels, and account config. Minor gaps: no delete permanently, inbox refresh or mark-as-spam operation, but agents can work around these.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources