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
      117 npm
      MIT

    • ProtonMail MCP Server

      robotben
      F
      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
      -

    • 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
      10 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
      167 npm
      11
      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.
      1
      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.1/5.0

    Scored across 39 tools

    Disambiguation3/5

    Within each product many tools are distinct, but the suite has multiple overlapping diagnostic/status tools: proton_bridge_status, proton_bridge_health, proton_bridge_info, proton_suite_status, proton_ecosystem_health, and multiple drive status/auth tools. Descriptions help, but an agent can still struggle to choose the right health/status/info tool.

    Naming Consistency5/5

    All tool names use lower snake_case with a consistent proton_ prefix, and product-specific tools follow predictable proton_<product>_<action> patterns. The mail tools omit an explicit mail namespace, but their action names are still clear and consistent.

    Tool Count2/5

    39 tools is excessive for a single MCP server, even one covering Mail, Drive, Bridge, and ecosystem diagnostics. While each product subgroup is individually scoped, the total surface creates substantial selection burden.

    Completeness4/5

    Core email and drive lifecycle operations are well covered: folder management, read/search/send/reply/forward/flag/move/delete, attachments, upload/download/copy/move/remove/share, and bridge/ecosystem diagnostics. Minor gaps exist around draft management, drive rename/search, and actual bridge process control.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources