x=hub

your toolset

    build deployment
    sign in

    Proton Bridge MCP

    mcpother official scanned
    com.considus/proton-bridge-mcp · v1.2.2
    deploy just this

    Read, organise and carefully-gated send for Proton Mail, without your mail leaving this machine.

    run it

    nothing to build
    No DockerfileThe worker built github.com/considus/proton-bridge-mcp for v1.2.2 on 2026-10-17 and found no Dockerfile, so there is nothing to build until a new version arrives. Its source is at github.com/Considus/proton-bridge-mcp.

    connect to it

    copy what your client needs
    {
  "mcpServers": {
    "proton-bridge": {
      "command": "CHANGE_ME",
      "args": []
    }
  }
}
    #!/usr/bin/env bash
# Registers every server with Claude Code (run once; `claude mcp list` to check).
set -euo pipefail
set -a; [ -f .env ] && source .env; set +a
claude mcp add proton-bridge -- CHANGE_ME

    {
  "mcpServers": {
    "proton-bridge": {
      "command": "CHANGE_ME",
      "args": []
    }
  }
}
    {
  "servers": {
    "proton-bridge": {
      "type": "stdio",
      "command": "CHANGE_ME",
      "args": []
    }
  }
}
    name: my-agent
target: local
servers:
- hub: com.considus/proton-bridge-mcp
    • not probed yet: tools unpinned, ingest lists them
    • nothing to build: the worker found no Dockerfile in github.com/considus/proton-bridge-mcp on v1.2.2; fill the files by hand

    tools

    Probe result: faileddocker: sandbox: docker build: timed out after 900 s

    runs · 2

    the latest tests of this entry by the hub and its workers, newest first
    dateworkermethodstatussandboxreason
    2026-10-18 13:02 local-mac-vm docker failed gvisor docker: sandbox: docker build: timed out after 900 s
    2026-10-17 15:17 local-mac-vm docker failed gvisor docker: sandbox: docker build: ERROR: failed to build: failed to solve: failed to read dockerfile: open Dockerfile: no such file or directory