Proton Safe MCP
Draft-only local Proton Mail MCP server that reads mail and stages drafts for manual sending.
Tested on Linux
Use it
Linux x86_64
You need first
- Runtimes:
Python 3.11–3.14 - System packages:
gnome-keyring or compatible Secret Service keyring
Install proton-safe-mcp via uv tool
uv tool install proton-safe-mcp==2.3.2
Check that it works
proton-safe-mcp --helpThe output should contain “usage: proton-safe-mcp”.
First thing to try
proton-safe-mcp doctorAdd it to your agent
claude mcp add proton-safe-mcp -e PROTON_BRIDGE_USER='<PROTON_BRIDGE_USER>' -- proton-safe-mcp serveJSON for Claude Desktop, Cursor and other clients
{
"mcpServers": {
"proton-safe-mcp": {
"command": "proton-safe-mcp",
"args": [
"serve"
],
"env": {
"PROTON_BRIDGE_USER": "<PROTON_BRIDGE_USER>"
}
}
}
}You fill in
PROTON_BRIDGE_USER: Proton address configured in Bridge (required)
Ask the user for PROTON_BRIDGE_USER; pickfit never had a value, so these are placeholders.
Run proton-safe-mcp doctor to check your setup, then add proton-safe-mcp as a server in your MCP client.
What it does
- Read and search your Proton Mail messagesNot tested
- Create draft emails with attachmentsNot tested
- Read PDF, TXT and CSV attachments as textNot tested
How far pickfit got
Linux x86_64
- Installs
- Connects
- 0 of 3 features work
- Works offline
Good for
- read and search Proton Mail messages
- create draft emails with attachments
- inspect bounded text from PDF, TXT and CSV attachments
- review drafts in Proton Mail and send manually
How pickfit tested it
Each run starts from a clean machine and follows the steps above. How pickfit verifies
Linux x86_64
An MCP client called one of its tools
- Replayed from scratch
- Works offline
- Checked on 30 Oct 2026
- Version 2.3.2
An MCP client handshake over stdio listed 13 tools, and a call to list_sender_addresses returned a result.
Differences the test machine hit
- README: PROTON_BRIDGE_USER required for Bridge connection
In the test: server exits before initialize with 'Error: PROTON_BRIDGE_USER is required'; handshake and tool calls need PROTON_BRIDGE_USER set (e.g. PROTON_BRIDGE_USER="test@example.com" prefix) even for local-only tools