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/IMAP3167 npm6MIT
- 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.614 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.67 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.5 npmMIT
- AlicenseAqualityBmaintenanceEnables 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.4204 npm1MIT
- AlicenseAqualityCmaintenanceEnables AI agents to send, read, search, and organize emails via ProtonMail using Proton Bridge. Supports MCP-compatible clients like Claude and Cursor.179 npm4MIT
TDQS
Scored across 34 tools
Every tool targets a specific action and resource: read vs. view vs. save attachments are clearly separated by content type, single vs. bulk variants are explicitly described for one or many messages, and reply/draft/send/forward each serve distinct lifecycle stages. No two tools are functionally interchangeable without a clear scope difference.
The vast majority of tools follow a consistent verb_noun pattern (e.g., list_folders, read_message, create_draft), and all names are lowercase with underscores. Minor deviations like folder_status (noun_noun) and bulk_* prefixes (adverb_verb) introduce slight inconsistency, but the pattern remains predictable and readable.
At 34 tools, the server exceeds the 25-tool threshold and feels heavy for a mail client. The bulk/single pairs for mark, label, and remove_label add redundancy that could be consolidated with array parameters, and the attachment-specific tools (read, view, save, purge) could potentially be merged.
The tool surface covers core email workflows comprehensively: reading, searching, sending, replying, drafting, labels, folders, attachments, and even security headers. Minor gaps include no permanent message deletion, no rename operation for folders/labels, and no dedicated 'list all messages' that doesn't rely on search filters, but these are workaroundable.