Skip to main content
Glama
googlarz

Proton Mail Bridge MCP

Related Servers

Alternatives to Proton Mail Bridge MCP

  • F
    license
    Not graded
    quality
    F
    maintenance
    Enables comprehensive ProtonMail management through SMTP and IMAP, supporting email sending/reading, folder operations, analytics, and contact tracking with advanced search and automation capabilities.
    43
    -

Related Servers

  • 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
  • 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
    Not graded
    quality
    C
    maintenance
    Enables AI clients to interact with ProtonMail accounts through the Proton Bridge using SMTP and IMAP protocols. Provides email management capabilities via secure local bridge connections.
    8 npm
    MIT
  • 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
  • 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

TDQS

A3.8/5.0

Scored across 96 tools

Disambiguation2/5

Despite extensive cross-referencing in descriptions, several tool clusters have genuinely fuzzy boundaries: analytics tools (get_email_stats, get_email_analytics, get_volume_trends, top_senders) overlap heavily, and bulk_delete/batch_email_action/bulk_move/bulk_update_flags/bulk_update_labels split the same conceptual operation by action type. With 96 tools, an agent faces real misselection risk when choosing between list_drafts vs list_remote_drafts or search_emails vs search_indexed_emails without reading very long descriptions carefully.

Naming Consistency4/5

The dominant pattern is consistent lowercase verb_noun (list_snoozed, create_draft, delete_folder, send_email, get_threads), which is easy to predict. Minor deviations prevent a 5: 'bulk_*' vs 'batch_*' prefixes are used interchangeably for similar operations, and a few phrasal verbs (run_doctor, wait_for_mailbox_changes, clear_index) break the otherwise uniform rhythm.

Tool Count1/5

At 96 tools this is an extreme count, exceeding the stated 50+ threshold for a 1 even though mail management is a broad domain. The surface could be significantly consolidated: analytics could collapse into one parameterized tool, bulk/batch operations could share a single action dispatcher, and attachment save/get variants could be unified.

Completeness5/5

The domain coverage is exceptionally thorough: send/draft/review flows, scheduling and snooze with cancel paths, full folder/label CRUD, thread lifecycle actions, attachments with multiple retrieval strategies, templates with rendering, indexing and sync, analytics, import/export, and diagnostics. Nearly every mutation has a reversible counterpart or a clear 'prefer X' alternative, leaving no obvious dead ends.

Maintenance

ActivityActive
ResponsivenessSlow