Skip to main content
Glama
openmaxai

@openmaxai/email-mcp

by openmaxai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @openmaxai/email-mcp

No user-submitted related servers found.

    Related Servers

    • Mail MCP Server

      martinzarfl
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to send, read, and manage emails via SMTP and IMAP, with support for attachments, threads, and mailbox organization.
      16
      6 npm
      1
      MIT

    • phison-mail-mcp

      Kinolian1107
      F
      license
      B
      quality
      D
      maintenance
      Enables AI models to send, receive, search, and manage emails via SMTP/IMAP, including support for attachments, contacts, and advanced search.
      18
      -

    • mcp-imap

      andrewmalov
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with email accounts via IMAP and SMTP, supporting mailbox listing, email search, retrieval, sending, and management.
      MIT

    • better-email-mcp

      laschopin
      A
      license
      Not graded
      quality
      C
      maintenance
      IMAP/SMTP email for AI agents -- read, send, organize folders, and manage attachments across multiple accounts, with auto-discovery.
      MIT

    • IMAP Email MCP Server

      jdickey1
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to read, search, compose, and send emails by connecting to any IMAP/SMTP provider. It supports comprehensive mailbox management, including draft handling and message deletion, directly through natural language.
      10
      209 npm
      10
      MIT

    • MCP Email

      voiesdegypte
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to read, send, organize, and search emails across multiple IMAP/SMTP mailboxes.
      1,026 npm
      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 7 tools

    Disambiguation5/5

    Each tool targets a distinct email operation: sending, replying, listing, reading, searching, managing folders, and toggling read status. Even though list_emails and search_emails both return messages, their purposes are clearly separated by folder listing vs. substring search.

    Naming Consistency5/5

    All tool names consistently follow a verb_noun pattern: send_email, reply_email, list_emails, get_email, search_emails, mark_read, list_folders. This makes the tool set highly predictable and easy for an agent to navigate.

    Tool Count5/5

    Seven tools is well-scoped for an email MCP server. Each tool covers a meaningful operation without redundancy or bloat.

    Completeness4/5

    Core email workflows are well covered: send, reply, list, search, read, mark read, and folder listing. Minor gaps exist around operations like deleting/moving messages or sending attachments, but agents can typically accomplish common email tasks without dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources