Skip to main content
Glama
Iniciativas-Alexendros

Proton Suite Agent

by Iniciativas-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
      86 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

    A3.5/5.0

    Scored across 39 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose, grouped by product area (bridge, drive, mailbox, ecosystem, agent). Within email, tools are separated by action (list, search, get, send, reply, forward, flag, move, delete) with no overlap. Drive operations are similarly distinct. No ambiguity between tools.

    Naming Consistency5/5

    All tools follow a consistent pattern: proton_<product>_<verb>_<noun> (e.g., proton_list_emails, proton_drive_upload, proton_bridge_login). No mixing of styles or inconsistent verb forms.

    Tool Count4/5

    With 39 tools, the server is comprehensive but slightly heavy. However, it covers multiple sub-products (Mail, Bridge, Drive, Ecosystem, Agent), each requiring several tools. The count is justified by the breadth, though it exceeds the typical 15-tool sweet spot.

    Completeness5/5

    The tool surface is complete for the Proton Suite domain: email CRUD (send, receive, search, flag, move, delete), drive file management (upload, download, organize, share), bridge and ecosystem status/management, and even agent planning. No obvious gaps for common workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources