Skip to main content
Glama
Sign In
mcp-proton-mail

mcp-proton-mail

by legalaspro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-proton-mail

No user-submitted related servers found.

    Related Servers

    • proton-mail-mcp

      sethbang
      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
      79 npm
      8
      MIT

    • protonmail-mcp-server

      de-Blanck
      A
      license
      A
      quality
      D
      maintenance
      A 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.
      4
      19 npm
      1
      MIT

    • Proton Workflow Connector

      NtrpyDev
      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.
      MIT

    • ProtonMail MCP Server

      robotben
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that connects to ProtonMail via Bridge, enabling AI assistants like Claude to manage your email.
      3
      MIT

    • Proton Mail MCP

      galengreen
      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.
      79 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 30 tools

    Disambiguation4/5

    Most tools map to a distinct resource/action, and the descriptions explicitly disambiguate the risky pairs such as show_thread vs read_thread and preview_action vs the dedicated preview tools. The main residual confusion is the large preview/apply lifecycle family and the coexistence of server-applied rules versus Proton Sieve filters, though the text clearly routes between them.

    Naming Consistency4/5

    The names are overwhelmingly snake_case and verb-first, with predictable forms like search_mail, read_thread, create_draft, preview_rules, and apply_rules. Minor deviations exist in bare verbs such as move, label, unsubscribe, and reindex, but the convention remains readable and mostly consistent.

    Tool Count2/5

    Thirty tools is over the reasonable range for this surface, largely due to paired preview/execute tools and separate rule, Sieve, folder, and action flows. While each tool has a role, the set is heavy enough that it would be easier to misuse than a tighter 12-18 tool design.

    Completeness3/5

    The surface is broad: search, read, threads, attachments, drafts, forwarding, moves, labels, read state, unsubscribe, folders, rules, reindex, undo, and audit are covered. However, there is no send operation, no list_folders or list_labels discovery tool, and no true draft editing/update path, which leaves notable gaps for a mail server.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources