Thin Python wrapper (pip/uvx installable) for the proton-bridge-mcp MCP server, which reads/searches Proton Mail via Proton Mail Bridge. Requires Node.js; runs the real Node implementation via npx.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"alpha-romer-coma-proton-bridge-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# proton-bridge-mcp (Python wrapper) A `pip`/`uvx`-installable wrapper around [`proton-bridge-mcp`](https://github.com/alpharomercoma/proton-bridge-mcp), an [MCP](https://modelcontextprotocol.io) server for reading and searching Proton Mail via Proton Mail Bridge. **This package contains no Python implementation.** It's a thin shim that execs into the real Node.js implementation via `npx`. It exists so Python-oriented MCP tooling (`uvx`, `pipx`, `pip install`) can install and run it without needing to know it's Node underneath. Unofficial, community project. Not affiliated with or endorsed by Proton AG. ## Requirements - **Node.js 18+** must be installed and on `PATH` (specifically `npx`). This wrapper cannot function without it — there is no pure-Python fallback. - A Proton Mail plan that supports Bridge, with [Proton Mail Bridge](https://proton.me/mail/bridge) running ## Install ```bash pip install proton-bridge-mcp # or uvx proton-bridge-mcp ``` ## Setup Run the interactive setup wizard once (fetches and pins Bridge's TLS certificate, verifies login, writes credentials to `~/.config/proton-bridge-mcp/`, chmod 600): ```bash proton-bridge-mcp-setup ``` ## Register with an MCP client **Claude Code:** ```bash claude mcp add proton-mail -s user -- proton-bridge-mcp ``` **Claude Desktop / other MCP clients:** ```json { "mcpServers": { "proton-mail": { "command": "proton-bridge-mcp" } } } ``` **Codex CLI:** Tested end-to-end against Codex CLI 0.146.0 via `uvx`, with a real Bridge connection and real tool calls. MCP support is behind an under-development feature flag as of 0.146.0 — enable it once: ```bash codex features enable mcp_2026_07_28 ``` Then register the server: ```bash codex mcp add proton-mail -- uvx proton-bridge-mcp ``` `uvx` resolves and caches per exact version, so (unlike a bare `npx` invocation of the underlying npm package) it isn't at risk of silently picking up a stale global install — no version pinning needed…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.