proton-bridge-mcp
Related Servers
Alternatives to proton-bridge-mcp
- AlicenseAqualityCmaintenanceUnofficial MCP server for Proton Mail (not affiliated with Proton AG) — send, read, search & organize email over SMTP/IMAP3183 npm7MIT
- AlicenseAqualityBmaintenanceAn MCP server that enables AI assistants to read and search Proton Mail messages through a locally running Proton Mail Bridge. It provides tools like list_folders, list_messages, search_messages, get_message, and get_attachment.64 npmMIT
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with a Proton Mail mailbox through Proton Bridge, supporting listing, searching, reading, sending, and organizing emails.-
- AlicenseBqualityBmaintenanceEnables AI assistants to read, search, send, reply, and organize ProtonMail emails through a local ProtonMail Bridge, with automatic Bridge discovery and pinned TLS verification.23LGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to send, read, search, and organize email from Proton Mail accounts via SMTP and IMAP.83 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables 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.10 npmMIT
- AlicenseAqualityCmaintenanceEnables 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.425 npm2MIT
- AlicenseAqualityAmaintenanceEnables AI agents to send, read, search, and organize emails via ProtonMail using Proton Bridge. Supports MCP-compatible clients like Claude and Cursor.1813 npm4MIT
TDQS
Scored across 25 tools
Most tools target a distinct resource-action pair, and the descriptions make boundaries clear (e.g., apply_label vs. remove_label vs. delete_label; read_message vs. get_headers). The few potentially confusable areas are sending pathways (send, send_draft, reply, forward) and attachment handling (list_attachments, read_attachment, save_attachment), but each has a clear stated role.
Names are consistently snake_case and mostly follow verb_noun form (list_folders, read_message, create_draft, move_to_folder). A handful use single verbs (send, forward, reply, mark, unsubscribe), which is readable and conventional but slightly less uniform than the rest.
The 25-tool surface covers a broad email client domain, but it sits at the heavy end for an MCP server and includes several operations that could plausibly be consolidated (label/folder management, attachment lifecycle). Each tool has a reason to exist, yet the set feels large rather than tightly scoped.
Coverage is strong across reading, searching, threading, labels/folders, drafts, sending, forwarding, replying, attachments, marking, and unsubscribe flows. Minor gaps remain, notably no folder deletion and no permanent message deletion or empty-trash operation, only moves to Trash.