Proton Mail MCP runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 25 Oct 2026.
Proton Mail MCP via Bridge (IMAP/SMTP) · 13 tools · dual transport stdio + HTTP.
What changed 2
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 August 2026. No other catalogue keeps this.
What the code does
We read the source, 6 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
child = spawn(opts.file, [...(opts.args ?? [])], {
COPY package.json pnpm-lock.yaml pnpm-workspace.yaml .npmrc ./
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add proton-mail-mcp -e 'PROTON_USERNAME=<PROTON_USERNAME>' -e 'PROTON_PASSWORD=<PROTON_PASSWORD>' -- npx -y @alexendros/proton-mail-mcp{
"mcpServers": {
"proton-mail-mcp": {
"command": "npx",
"args": [
"-y",
"@alexendros/proton-mail-mcp"
],
"env": {
"PROTON_PASSWORD": "<PROTON_PASSWORD>",
"PROTON_USERNAME": "<PROTON_USERNAME>"
}
}
}
}[mcp_servers.proton-mail-mcp]
command = "npx"
args = ["-y", "@alexendros/proton-mail-mcp"]
env = { PROTON_USERNAME = "<PROTON_USERNAME>", PROTON_PASSWORD = "<PROTON_PASSWORD>" }{
"mcpServers": {
"proton-mail-mcp": {
"command": "npx",
"args": [
"-y",
"@alexendros/proton-mail-mcp"
],
"env": {
"PROTON_PASSWORD": "<PROTON_PASSWORD>",
"PROTON_USERNAME": "<PROTON_USERNAME>"
}
}
}
}{
"servers": {
"proton-mail-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@alexendros/proton-mail-mcp"
],
"env": {
"PROTON_PASSWORD": "<PROTON_PASSWORD>",
"PROTON_USERNAME": "<PROTON_USERNAME>"
}
}
}
}Put your own values in place of
<PROTON_USERNAME> (Bridge username (your Proton Mail address)), <PROTON_PASSWORD> (Bridge-generated app password (NOT your Proton account password)).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
PROTON_BRIDGE_HOST (Hostname or IP of the Proton Mail Bridge (default: 127.0.0.1 for local, or container hostname in compose)), PROTON_IMAP_PORT (IMAP port exposed by Proton Mail Bridge (default: 1143)), PROTON_SMTP_PORT (SMTP port exposed by Proton Mail Bridge (default: 1025)).
Alternatives to Proton Mail MCP
same job, measured the same wayIMAP/SMTP email MCP server — 52 tools, stdio + HTTP, IMAP IDLE push, multi-account, AI triage.
MCP server for serial port communication. 25 tools, resources, prompts, and stdio/HTTP transports.
MCP server for AI agent bank accounts on Sui — 23 tools, 15 prompts, stdio transport
Next.js development tools MCP server with stdio transport
ROOT-based MCP server exposing root_python and root_cpp tools (stdio transport).
Forge Space MCP server for UI and backend generation via stdio transport.
Read Proton Mail and save drafts through your local Proton Mail Bridge.
Local MCP server for Weeek (stdio transport) — read-only by default, opt-in write tools.
Proton Mail MCP — questions
Answers built from our own checks of this server.