Skip to main content
Glama
Soluciones-Alexendros

Proton Suite Agent

by Soluciones-Alexendros
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Proton Suite Agent

No user-submitted related servers found.

    Related Servers

    • protonmail-mcp

      apexxapps
      A
      license
      A
      quality
      B
      maintenance
      MCP server that gives AI coding agents access to ProtonMail via Proton Bridge, enabling secure search, read, draft, and send of emails while keeping decrypted mail local.
      8
      15 npm
      MIT

    • ProtonMail MCP Server

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

    • proton-mcp

      RndmJoker
      A
      license
      A
      quality
      B
      maintenance
      An 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.
      6
      4 npm
      MIT

    • mailpouch

      chandshy
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that gives AI agents permission-gated, audit-logged access to private email providers (Proton Mail via Bridge and plain IMAP), running locally with OAuth-based authentication and human-controlled escalation for destructive operations.
      66
      40 npm
      14
      MIT

    • corresync

      nkiyohara
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that unifies email and calendar management across multiple providers, enabling AI agents to search, read, and write with explicit approval and local-first security.
      2
      Apache 2.0
    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

    B3/5.0

    Scored across 39 tools

    Disambiguation3/5

    Core mail and Drive actions are distinct, but health/status/info tools overlap heavily across bridge, drive, ecosystem, and suite (e.g. proton_bridge_status vs proton_bridge_health vs proton_bridge_info; proton_drive_status vs proton_drive_auth_status). Descriptions help, but an agent can still struggle to pick the right status or diagnostic tool.

    Naming Consistency4/5

    All names use snake_case with a proton_ prefix and verb_noun order, which is highly predictable. However, mail tools omit a proton_mail_/bridge_ prefix while Drive tools use proton_drive_, creating a minor inconsistency in prefixing.

    Tool Count2/5

    39 tools is a heavy surface for one MCP server; the broad Proton suite partially justifies it, but redundant status/health/info and audit/format_report variants mean not every tool clearly earns its place. This volume increases selection cost for agents.

    Completeness4/5

    Core Drive and Mail lifecycles are well covered: list/search/get/send/reply/forward/flag/move/delete for mail, and list/upload/download/copy/move/remove/share for Drive. Minor gaps remain, such as mailbox folder rename/delete and Drive share management, but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources