Skip to main content
Glama
SinoEdwards

Mail Agent MCP

by SinoEdwards
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Mail Agent MCP

No user-submitted related servers found.

    Related Servers

    • Email MCP Server

      tianpeijun
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI to send, read, search, delete and reply to emails through SMTP or Gmail API, supporting common email services like QQ, 163, Gmail and Outlook with HTML/text formats and attachments.
      19 npm
      1
      ISC

    • 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

    • Gmail MCP Pro

      Mr-Godot
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to interact with Gmail accounts through IMAP/SMTP, supporting reading, sending, replying to emails, managing threads, downloading attachments, and searching with Gmail syntax using simple app password authentication.
      -

    • 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 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

    B3.2/5.0

    Scored across 41 tools

    Disambiguation4/5

    Most tools target a distinct resource and action, with descriptions that cross-reference lookalikes (search vs latest, flag vs keyword, single vs bulk delete). A few clusters such as delete_spam/delete_by_domain/bulk_delete_by_searcch and the preview_send/reply/forward variants could still cause misselection.

    Naming Consistency3/5

    The imap_ prefix and generally verb_noun structure help, but conventions are mixed: delete vs remove (delete_email vs remove_keyword), get/find/search for lookup tools, folder_status and doman_stats are noun phrases, and connect/disconnect lack an explicit object.

    Tool Count2/5

    41 tools is well above the 25+ threshold for a heavy toolset. The broad email domain justifies some sprawl, but the many delete, spam, folder, and flag variants make the surface feel overly large and harder for an agent to navigate efficiently.

    Completeness3/5

    Core mail workflows such as search, read, send via preview/confim, delete, move, and flagging are well covered. However, whitelist management has no remove counterpart, folders cannot be renamed or deleted, and there is no copy-email tool, leaving some obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources