proton-mcp-server
Provides read-only access to Proton Mail via MCP, enabling AI agents to list accounts/folders, search messages, and read emails using Proton Mail Bridge's local IMAP server.
README
Proton Mail MCP Server
Read-only access to Proton Mail for AI agents (such as Hermes) over the Model Context Protocol (stdio transport).
Mail is read from Proton Mail Bridge, which runs a local IMAP server. The MCP server wraps that IMAP server and exposes a small set of tools. Multiple Proton accounts are supported and selected by name on each tool call.
Read-only by design: listing folders/messages, searching, and reading a message. Sending or moving/deleting mail is intentionally out of scope.
How it works
+----------+ stdio/stdin+stdout +---------------------+ IMAP (local) +---------------------+
| Agent | <---------------------> | proton-mcp-server | <------------> | Proton Mail Bridge |
| (Hermes) | MCP (JSON-RPC) | (this package) | 127.0.0.1:1143 | (protonmail-bridge)|
+----------+ +---------------------+ +---------------------+
Proton Mail Bridge must be installed, signed in, and running. In the Bridge GUI, for each account enable the IMAP/SMTP client and copy the generated password (this is not your Proton account password).
Install
Requires Python 3.11+. Using uv (recommended):
git clone <this repo> && cd proton-mcp-server
uv sync # create venv + install dependencies
Or with pip into a venv of your choice: pip install .
The proton-mcp-server console script is provided.
Configure accounts
Create a config file listing each account (see config.example.toml):
mkdir -p "${XDG_CONFIG_HOME:-$HOME/.config}/proton-mcp"
cp config.example.toml "${XDG_CONFIG_HOME:-$HOME/.config}/proton-mcp/config.toml"
# then edit it with your bridge username + generated password
Config-file lookup order (first wins):
--config PATHCLI flagPROTON_MCP_CONFIGenvironment variable$XDG_CONFIG_HOME/proton-mcp/config.toml(default~/.config/proton-mcp/config.toml)
[[accounts]] fields:
| field | required | default | notes |
|---|---|---|---|
name |
yes | — | Unique label agents pass as the account argument. |
username |
yes | — | Your Proton address (the IMAP login name). |
password |
yes | — | Password generated by Proton Mail Bridge, not Proton. |
host |
no | 127.0.0.1 |
Bridge listens on localhost. |
port |
no | 1143 |
Bridge IMAP port. |
security |
no | starttls |
starttls (Bridge v3 default), ssl (TLS from start), plain. |
Tools
| tool | description |
|---|---|
list_accounts |
List configured account names. |
list_folders |
List mailboxes for an account (INBOX, Sent, …). |
list_messages |
List recent messages in a folder, newest first. |
search_messages |
Search a folder by subject/from/to/cc/body/text. |
get_message |
Fetch and render a full message by UID. |
Run proton-mcp-server --list-accounts to smoke-test the config (this does
not require Bridge to be reachable — it only parses the file).
Use with Hermes
Add the server to your Hermes MCP configuration (stdio server):
{
"mcpServers": {
"proton-mail": {
"command": "/abs/path/to/proton-mcp-server/.venv/bin/proton-mcp-server",
"env": { "PROTON_MCP_CONFIG": "/abs/path/to/proton-mcp/config.toml" }
}
}
}
(Or omit env if you use the default config path.) Then ask Hermes to read
your mail; it will discover the tools via MCP.
Develop / debug
uv sync
uv run proton-mcp-server --help
uv run proton-mcp-server --print-config-path
uv run proton-mcp-server --list-accounts
To inspect the protocol by hand, pipe a JSON-RPC initialize + tools/list
exchange into the running server over stdio.
Security notes
- Config holds bridge passwords; keep it readable only by you (
chmod 600).config.tomlis git-ignored by default. - The connection to Proton Mail Bridge is localhost only. The default
security = "starttls"upgrades to TLS via STARTTLS after connecting; the Bridge's local self-signed certificate is accepted with verification disabled (the connection never leaves localhost).security = "ssl"(TLS from connection start) andsecurity = "plain"(no encryption) are also available. The server never connects to a remote host with verification off — and all connection fields are configurable per account. - All operations are read-only (BODY.PEEK, no STORE/EXPUNGE).
License
MIT — see LICENSE.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.