Skip to main content
Glama
sethbang

proton-mail-mcp

by sethbang

Related Servers

Alternatives to proton-mail-mcp

  • A
    license
    A
    quality
    D
    maintenance
    A Model Context Protocol server that enables AI assistants to interact with Proton Drive files, supporting operations like listing, reading, creating, and deleting files and folders.
    7
    79 npm
    17
    MIT

Related Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Self-hosted MCP server that enables reading, sending, and automating Proton Mail via Bridge, with optional SimpleLogin alias management.
    22 PyPI
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    An 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.
    23 npm
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables 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
  • A
    license
    Not graded
    quality
    C
    maintenance
    Lets MCP clients read, search, draft, move, label, and delete mail through a locally running Proton Mail Bridge connection, so messages never leave your machine. Sending is off by default, deletions only move mail to Trash, and draft attachments are restricted to approved folders.
    23 npm
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    MCP 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.
    4
    17 PyPI
    MIT

TDQS

A4.2/5.0

Scored across 31 tools

Disambiguation4/5

Most tools have clearly distinct purposes, but pairs like reply_email/reply_all_email and thread vs. single-message tools (move_thread/move_message) could cause minor confusion. Descriptions do a good job clarifying usage.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_folder, delete_message, update_message_flags). The naming convention is uniform across the entire set.

Tool Count3/5

At 31 tools, the set is larger than typical (3-15) but still justified by the breadth of email operations (folders, labels, messages, threads, bulk actions, stats, attachments). It feels slightly heavy but not excessive.

Completeness5/5

The tool surface covers all major email lifecycle operations: folder/label CRUD, message send/reply/forward/draft, move/delete (single and bulk), thread operations, search, stats, and attachments. No obvious gaps for core email tasks.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive