Proton MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROTON_PASS | Yes | Your Proton Mail Bridge password | |
| PROTON_USER | Yes | Your Proton Mail email address used for Bridge authentication | |
| PROTON_IMAP_HOST | Yes | IMAP server host for Proton Mail Bridge (usually 127.0.0.1) | 127.0.0.1 |
| PROTON_IMAP_PORT | Yes | IMAP server port for Proton Mail Bridge (usually 1143) | 1143 |
| PROTON_SMTP_HOST | Yes | SMTP server host for Proton Mail Bridge (usually 127.0.0.1) | 127.0.0.1 |
| PROTON_SMTP_PORT | Yes | SMTP server port for Proton Mail Bridge (usually 1025) | 1025 |
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 |
|---|---|
| proton_list_foldersA | List all mailbox folders (INBOX, Sent, Drafts, Trash, etc.) with message counts and unread counts |
| proton_list_emailsA | List emails in a specific folder with pagination. Shows sender, subject, date, and read status. Results are newest first. |
| proton_search_emailsA | Search emails by sender, recipient, subject, date range, body content, or unread status. Multiple criteria are combined with AND logic. |
| proton_read_emailA | Read the complete content of an email, including headers, body, and attachments. Specify folder and email UID. |
| proton_send_emailB | Send a new email. Supports plain text and HTML formats. Recipients can be a single string or array of strings. |
| proton_reply_emailA | Send a reply to an existing email. Properly sets In-Reply-To and References headers for threading. Can reply to all or just the sender. |
| proton_move_emailB | Move an email from one folder to another. Specify source folder, email UID, and destination folder. |
| proton_delete_emailA | Delete an email by moving it to the Trash folder. Use the folder name and email 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 8 tools
Each tool has a clearly distinct purpose targeting specific email operations: listing, reading, sending, replying, searching, moving, deleting, and folder management. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent 'proton_verb_noun' pattern using snake_case, such as proton_list_emails and proton_send_email. This uniformity enhances readability and predictability across the toolset.
With 8 tools, the server is well-scoped for email management, covering essential operations like CRUD (create, read, update via move/reply, delete), search, and folder handling. Each tool serves a clear purpose without redundancy.
The toolset provides complete coverage for email workflows, including listing, reading, sending, replying, searching, moving, deleting, and folder management. There are no obvious gaps, enabling agents to handle full email lifecycle tasks effectively.