Skip to main content
Glama
Sign In
Proton Suite Agent

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
      D
      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
      30 npm
      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-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.
      29
      403 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
      60 npm
      17
      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 mostly distinct, but the set has several overlapping status/health tools: proton_ecosystem_health vs proton_suite_status, proton_bridge_health vs proton_bridge_status vs proton_bridge_info, and proton_drive_auth_status vs proton_drive_status. Descriptions clarify scope, but an agent can still hesitate over which status check to call.

    Naming Consistency4/5

    Tools consistently use the proton_ prefix and snake_case, generally following a proton_<domain>_<action>_<object> pattern. Minor deviations like proton_bridge_accounts (noun-only) and mixed domain labels (ecosystem/suite/bridge) are readable but slightly less predictable.

    Tool Count2/5

    39 tools is heavy for a single server, even one spanning mail, Drive, Bridge, and ecosystem administration. Many health/auth/status variants could be consolidated, and the large surface increases selection burden.

    Completeness4/5

    Mail and Drive lifecycles are broadly covered: listing, reading, sending, replying, forwarding, flagging, moving, deleting, attachments, uploads, downloads, sharing, auditing, and organizing. There are minor gaps such as no folder rename/delete for mail and limited Drive path rename/search, but core workflows are supported.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources