Skip to main content
Glama
ronamosa

ProtonMail MCP Server

by ronamosa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to ProtonMail MCP Server

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

    • protonmail-mcp

      dadamonis
      A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to read, search, send, reply, and organize ProtonMail emails through a local ProtonMail Bridge, with automatic Bridge discovery and pinned TLS verification.
      23
      LGPL 3.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.
      72 npm
      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

    • 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.
      25
      1
      Apache 2.0

    • proton-mcp-server

      QinZinn
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides read-only access to Proton Mail via MCP, enabling AI agents to list accounts/folders, search messages, and read emails using Proton Mail Bridge's local IMAP server.
      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 18 tools

    Disambiguation4/5

    Most tools target clearly distinct resources and actions (folders, emails, drafts, attachments, connection). Minor overlap between get_emails/get_email_by_id/search_emails and between sync_folders/get_folders, though descriptions differentiate list vs. fetch-by-id vs. search and refresh vs. list.

    Naming Consistency5/5

    Every tool follows a consistent snake_case verb_noun pattern (get_emails, create_draft, send_email, mark_email_read, move_email). The convention is applied uniformly across all 18 tools with no deviations.

    Tool Count4/5

    18 tools is slightly heavy but justified for a full email client spanning folders, reading, sending, drafts, attachments, search, and flags. Each tool earns its place with little redundancy.

    Completeness4/5

    Covers core lifecycle: list/read/search, send, draft create/update/send/delete, attachments, folders, move, delete, and flags. Gaps include direct reply/forward sending and thread/conversation views, but most workflows are workable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources