Skip to main content
Glama
combor

Baryon MCP

by combor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

Related Servers

Alternatives to Baryon MCP

No user-submitted related servers found.

    Related Servers

    • proton-bridge-mcp

      Considus
      A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to read, organize, and send Proton Mail through the local Proton Bridge, with careful gating for sending and attachment access.
      34
      1
      Apache 2.0

    • 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
      16 npm
      1
      MIT

    • ProtonMail MCP Server

      ronamosa
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to send, read, search, and organize emails via ProtonMail using Proton Bridge. Supports MCP-compatible clients like Claude and Cursor.
      17
      16 npm
      4
      MIT

    • ProtonScope

      dazzle-blip
      F
      license
      Not graded
      quality
      B
      maintenance
      A lightweight MCP server providing AI agents a scoped, read-and-draft-only view into Proton Mail via Proton Bridge, with code-enforced restrictions preventing external access or sending.
      -

    • ProtonBound

      dazzle-blip
      F
      license
      Not graded
      quality
      C
      maintenance
      A security-first MCP server that provides AI agents with a scoped, read-and-draft-only view into Proton Mail via Proton Bridge, ensuring no emails can be sent and access is restricted to configured workspaces.
      -

    • proton-mail-mcp

      graememeyer
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with a Proton Mail mailbox through Proton Bridge, supporting listing, searching, reading, sending, and organizing emails.
      -
    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.3/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools are clearly distinct: get_email vs get_thread vs list_emails vs search_emails are well-differentiated by scope (single message vs conversation vs folder listing vs search). The only mild overlap is get_attachment vs list_attachments vs save_attachment, but their descriptions clearly separate inline reading, listing metadata, and saving to disk.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern: get_attachment, get_email, get_thread, list_emails, search_emails, list_attachments, list_folders, list_sender_identities, save_attachment, save_draft, save_reply_draft. The verbs (get/list/search/save) are used predictably and consistently.

    Tool Count5/5

    11 tools is well-scoped for a Proton Mail MCP server. Each tool covers a distinct operation needed for email workflows: reading messages, searching, listing folders, managing attachments, and creating drafts. No redundant or extraneous tools.

    Completeness4/5

    The tool surface covers the core email workflow well: read (get_email, get_thread, list_emails, search_emails), attachments (list/get/save), and draft creation (save_draft, save_reply_draft). The only notable gap is that there is no tool to send a draft or manage folders (create/delete/rename), but the descriptions explicitly note sending stays with the user, so this appears intentional.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources