proton-bridge-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 has a clearly distinct role: listing mailboxes, listing messages, searching messages, and fetching a single message. No overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern (list_mailboxes, list_messages, search_messages, get_message) with uniform snake_case style.
Four tools is well-scoped for a read-only email client, covering the core needs without unnecessary bloat or unclear additions.
The tool set covers the primary read operations (list, search, get) but lacks write operations like send, delete, or mark as read, which are expected in a full email workflow.