proton-bridge-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROTON_BRIDGE_HOST | No | Bridge IMAP host. Default from credentials.json | |
| PROTON_BRIDGE_PORT | No | Bridge IMAP port. Default from credentials.json (default 1143) | 1143 |
| PROTON_BRIDGE_USER | No | Proton Mail address (Bridge user) | |
| PROTON_BRIDGE_CA_PATH | No | Path to pinned certificate PEM. Default is <config dir>/bridge-ca.pem | |
| PROTON_BRIDGE_MCP_HOME | No | Config directory. Default is ~/.config/proton-bridge-mcp | ~/.config/proton-bridge-mcp |
| PROTON_BRIDGE_PASSWORD | No | Bridge password (generated in Bridge app) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_mailboxesA | List all mail folders/mailboxes available on the Proton Mail account via Bridge. |
| list_messagesA | List the most recent messages in a mailbox (default INBOX), newest first. |
| search_messagesA | Search a mailbox by sender, subject, or body text. |
| get_messageB | Fetch the full parsed content (text/html body) of a single message by UID. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct action: listing mailboxes, listing messages, searching messages, and fetching a single message. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern: list_mailboxes, list_messages, search_messages, get_message. The naming is predictable and uniform.
With 4 tools, the set is well-scoped for a focused read-only email access use case. Each tool serves a clear purpose and none are redundant.
The toolset covers the primary read workflow: enumerate mailboxes, list messages, search, and fetch full content. However, it lacks send, draft, or message mutation capabilities, which are common in email tools but may be intentionally omitted for a read-only bridge interface.