protonmail-mcp-server
Related Servers
Alternatives to protonmail-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for reading and searching Proton Mail via Proton Mail Bridge, providing tools to list mailboxes, list/search messages, and get message details with TLS certificate pinning.4MIT
- AlicenseNot gradedqualityCmaintenanceSelf-hosted MCP server that enables reading, sending, and automating Proton Mail via Bridge, with optional SimpleLogin alias management.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that reads, searches, organizes, and deletes Proton Mail through the local Proton Mail Bridge, with read-only mode and sender authentication checks. It cannot send mail.83 npmMIT
- AlicenseAqualityCmaintenanceUnofficial MCP server for Proton Mail (not affiliated with Proton AG) — send, read, search & organize email over SMTP/IMAP3183 npm7MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to interact with Proton Mail through a self-hosted server that works alongside Proton Mail Bridge. It provides read-only mailbox tools such as listing folders, searching mail, and retrieving messages while keeping Bridge isolated from the network.MIT
- AlicenseAqualityDmaintenanceA read-only MCP server that connects to Proton Mail via Proton Bridge, enabling AI assistants to search, list, and read emails securely without leaving your machine.429 npm1MIT
TDQS
Scored across 29 tools
Most tools target clearly distinct resources or actions, and the detailed descriptions explicitly steer callers away from overlaps. However, move_email can also affect labels and can move to Trash, creating some inherent overlap with add_label/delete_email; check_new_emails and wait_for_new_email also share a watermark and purpose, with the main difference being whether they wait.
All tool names use consistent snake_case with predictable verb_noun or verb_object_state patterns. Variants such as mark_email_read/mark_email_unread, flag_email/unflag_email, and create_draft/create_reply_draft follow the same conventions throughout.
29 tools is heavy for a single email-client MCP and exceeds the 25-tool threshold in the rubric. While the domain is broad, many tools are thin variants (e.g., separate draft creators for send/reply/forward, read/unread and flag/unflag pairs) that could be consolidated or made mode-based.
Core email lifecycle coverage is strong: read/list/search, send/reply/forward, draft create/update/send, labels, flags, folders, attachments, threads, and new-mail watching are all present. Minor gaps remain, such as no explicit tool for mark answered/unanswered, no folder move/empty-trash operation, and no dedicated spam/ham marking beyond move_email.