Skip to main content
Glama
dadamonis

protonmail-mcp

by dadamonis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to protonmail-mcp

No user-submitted related servers found.

    Related Servers

    • proton-mail-mcp

      graememeyer
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with a Proton Mail mailbox through Proton Bridge, supporting listing, searching, reading, sending, and organizing emails.
      -

    • proton-bridge-mcp

      Considus
      A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to read, organize, and send Proton Mail through the local Proton Bridge, with careful gating for sending and attachment access.
      34
      1
      Apache 2.0

    • Proton Mail MCP Server

      fincher65
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to send, read, search, and organize email from Proton Mail accounts via SMTP and IMAP.
      73 npm
      MIT

    • proton-bridge-mcp

      alpharomercoma
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to read and search Proton Mail inbox through Proton Mail Bridge, providing tools to list mailboxes, list messages, search messages, and fetch full message bodies. Read-only, with secure certificate pinning.
      4
      11 npm
      1
      MIT

    • ProtonMail MCP Server

      ronamosa
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to send, read, search, and organize emails via ProtonMail using Proton Bridge. Supports MCP-compatible clients like Claude and Cursor.
      17
      16 npm
      4
      MIT

    • Proton Mail MCP Server

      fincher65
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to send, read, search, and organize Proton Mail email via SMTP and IMAP through the Model Context Protocol.
      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.3/5.0

    Scored across 23 tools

    Disambiguation3/5

    Most tools target distinct actions, but several boundaries blur: list_labels overlaps with list_mailboxes since labels appear as folders, create_mailbox can create labels when passed a Labels/ path, and remove_label vs delete_label could easily be confused. The descriptions help, but an agent still faces real misselection risk.

    Naming Consistency4/5

    The vast majority of tools follow a clear verb_noun snake_case pattern: list_emails, send_email, create_label, download_attachment. Exceptions like bridge_status and ping break the pattern slightly, but there is no chaotic mixing of styles.

    Tool Count3/5

    23 tools is on the heavy side for a single server and falls in the borderline range where each tool must clearly earn its place. Most tools are individually justified for a full email client, but the set feels larger than ideal and could be trimmed by merging health-check or label-related operations.

    Completeness4/5

    The tool surface covers the core email lifecycle well: list, get, search, send, reply, forward, draft, move, delete, mark, thread, attachments, folders, and labels. Notable gaps include no way to attach files when sending or replying, and no label rename/update operation, but agents can work around most of these gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources