Skip to main content
Glama
proton-mail-mcp

proton-mail-mcp

by jasen1300

Related Servers

Alternatives to proton-mail-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables full Proton Mail management through the Model Context Protocol by connecting to a local Proton Mail Bridge instance. It allows users to list, search, read, send, and organize emails using natural language commands.
      8
      2
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to send, read, search, and organize emails via ProtonMail using Proton Bridge. Supports MCP-compatible clients like Claude and Cursor.
      18
      19 npm
      4
      MIT
    • 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.
      -
    • 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
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to read a Proton Mail mailbox through a local Proton Bridge instance, listing folders, browsing recent messages, running full-text searches, and reading individual messages with decoded bodies and attachment info. All access is read-only — mailboxes are opened in IMAP READONLY mode, so nothing is ever modified, and the capability model lets operators opt into future draft, organize, send, and delete tools behind explicit confirmations.
      10
      180 PyPI
      MIT
    • A
      license
      A
      quality
      B
      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
      2
      Apache 2.0

    TDQS

    A3.5/5.0

    Scored across 31 tools

    Disambiguation4/5

    Most tools have sharply distinct purposes and the descriptions actively cross-reference each other (e.g. move_email vs add_label, ai_digest vs digest_bundle), which strongly reduces misselection. The weak spot is the analytics cluster — ai_triage, ai_digest, ai_analyze_email, digest_bundle and check_email_auth all read the mailbox and produce triage-style output, so an agent must read carefully to pick the right one.

    Naming Consistency4/5

    The dominant pattern is clear verb_noun: get_email, send_email, mark_email, move_email, delete_email, add_label, create_filter, list_mailboxes, search_emails. Deviations are minor but noticeable — noun-only or verb-less names like mailbox_stats, digest_bundle, surface_priority, extract_deadlines, and an 'ai_' prefix family (ai_triage, ai_digest, ai_analyze_email) that breaks the verb-first convention.

    Tool Count3/5

    At 31 tools this is on the heavy side for a mail server, and the surface is broad enough that each tool maps to a real operation, but several AI helpers could be consolidated into one parameterized tool. The count pushes past the point where an agent can hold the whole set in working memory, especially the five-tool analysis cluster.

    Completeness4/5

    Coverage is strong: full message CRUD, attachments, labels, filters, threading (get_thread/reply/forward), auth checks, stats, and both AI and free triage paths. The main gap is the draft lifecycle — create_draft exists but there is no list_drafts, update_draft, or send_draft, and there is no folder/mailbox creation since that is delegated to Proton.