Skip to main content
Glama

Related Servers

Alternatives to proton-mcp

No user-submitted related servers found.

    Related Servers

    • 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.
      105 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
      A
      quality
      C
      maintenance
      Unofficial MCP server for Proton Mail (not affiliated with Proton AG) — send, read, search & organize email over SMTP/IMAP
      31
      105 npm
      11
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to read and search Proton Mail and create draft-only emails with attachments through the local Proton Mail Bridge, while requiring out-of-band human approval before a draft can be committed.
      13
      74 PyPI
      6
      MIT
    • A
      license
      Not graded
      quality
      D
      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.
      105 npm
      MIT

    TDQS

    A4/5.0

    Scored across 6 tools

    Disambiguation4/5

    read_email, list_folders, list_sender_addresses, and send_email are clearly distinct resource+action pairs. The only real overlap is list_emails vs search_emails, which return the same header-only format from a folder; descriptions differentiate them (recent vs filtered) but an agent may still pick one when the other was intended.

    Naming Consistency5/5

    Every tool follows a consistent verb_noun snake_case pattern (read_email, list_folders, list_emails, search_emails, send_email) with list_sender_addresses the only longer name, still matching the schema. No mixed casing or vague bare verbs.

    Tool Count5/5

    Six tools is well-scoped for a focused mail client covering the read/list/search/send lifecycle. Each tool earns its place, and helper operations (sender addresses, folders) are exposed rather than hidden inside send_email.

    Completeness3/5

    The read-and-send workflow is fully covered, including threading and sender selection. However, a mail domain typically needs mailbox management — mark read/unread (read_email explicitly does not), move/archive/delete, and attachment handling — none of which exist, leaving dead ends for triage tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues