Skip to content

proton-safe-mcp v1.0.0

Choose a tag to compare

View all tags
@fbossiere fbossiere released this 29 Aug 07:25
· 14 commits to main since this release
v1.0.0
96424ef
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Overview

proton-safe-mcp v1.0.0 is the first stable release of a local, client-agnostic MCP server for Proton Mail through the official Proton Mail Bridge.

Safety boundary: the server can read and search mail and create human-approved drafts, but it deliberately cannot send, delete, or move messages, download received attachments, or accept client filesystem paths.

Highlights

  • Read-only IMAP tools for mailbox status, folders, message listing, search, and bounded plain-text reads using BODY.PEEK.
  • Client-neutral attachment staging with declared sizes, ordered base64 chunks, MIME allow-listing, SHA-256 verification, expiry, and single-use tokens.
  • Draft creation protected by an explicit, out-of-band local approval step that is not exposed through MCP.
  • Hardened local defaults: STDIO-only transport, Proton Bridge locked to 127.0.0.1, keyring-backed credentials, input-injection defenses, and private state files.
  • Typed Python 3.11+ package with contributor documentation, a security policy, issue templates, Dependabot, and automated CI.

Validation

Post-merge CI run #2 passed all seven jobs for 96424ef:

  • Ruff lint and formatting
  • mypy strict type checking
  • pytest on Python 3.11, 3.12, and 3.13
  • dependency audit with pip-audit
  • source and wheel distribution build

Requirements

  • Linux with Proton Mail Bridge installed, signed in, and running
  • A Proton plan that supports Bridge
  • Python 3.11 or newer
  • uv

See the README for installation and client configuration, the security policy for private vulnerability reporting, and PR #1 for the complete release review.

Assets 2
Loading