Skip to main content
Glama
Wh1isper

MCP Email Server

by Wh1isper
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to MCP Email Server

No user-submitted related servers found.

    Related Servers

    • cpanel-mail-mcp

      rosauceda
      A
      license
      A
      quality
      B
      maintenance
      Manages email accounts via IMAP/SMTP, enabling reading, searching, sending, replying, forwarding, and folder management with multi-user and OAuth support.
      22
      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

    • sse-email-mcp-server

      1018053166
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides email sending and receiving via SMTP/IMAP/POP3, supporting major email providers and dynamic authentication for AI assistant integration.
      6 npm
      4
      MIT

    • Email Server

      Code-MonkeyZhang
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables email management through IMAP and SMTP protocols, supporting reading, sending, replying to emails with proper threading, and downloading attachments. Supports multiple email accounts with flexible configuration options.
      1
      BSD 3-Clause

    • mcp-mail-server

      robotic-wings
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to read, search, and manage email via IMAP, and send emails with attachments via SMTP, using natural language commands.
      301 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

    A4.3/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools clearly target distinct email operations (list, read, send, delete, move, archive, attachments). The main overlaps are mark_emails_as_read vs set_email_flags and get_attachment_content vs download_attachment, but these are described as intentional conveniences with different behavior.

    Naming Consistency4/5

    Tool names mostly follow a clear verb_noun snake_case pattern like list_emails_metadata, delete_emails, and move_emails. Minor deviations such as mark_emails_as_read and save_to_mailbox are still readable but break the strict list_/get_/send_/delete_ symmetry.

    Tool Count4/5

    18 tools is slightly above the typical 3-15 tool range, but the count is justified by the breadth of email operations: listing, reading, sending, forwarding, saving drafts, deleting, moving, archiving, tagging, and attachments. It feels reasonably scoped rather than bloated.

    Completeness5/5

    The tool set covers the email lifecycle well: discovery, reading, searching metadata, sending, forwarding, saving drafts, deleting, moving, archiving, tagging, flags, and attachments. It also includes security-relevant allowlist tools for recipients and senders, so the domain feels fully covered.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources