protonmail-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROTON_BRIDGE_HOST | No | Bridge host | 127.0.0.1 |
| PROTON_BRIDGE_PORT | No | Bridge IMAP port | 1143 |
| PROTON_BRIDGE_USER | Yes | Bridge IMAP username (your email) | |
| PROTON_BRIDGE_PASSWORD | Yes | Bridge-generated IMAP password |
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 in the Proton Mail account with message counts and unread counts. Use this tool to discover available folders before listing or searching emails. Args:
Returns: A list of folders with path, message count, and unread count. Examples:
|
| proton_list_emailsA | List emails in a folder, sorted newest first, with pagination support. Returns email summaries (subject, from, date, snippet) — not full bodies. Use proton_get_email to read an individual email's full content. Args:
Returns: Paginated list of email summaries with total count and pagination metadata. Examples:
|
| proton_get_emailA | Retrieve a single email's full content by its IMAP UID, including body text and attachment metadata. Use proton_list_emails or proton_search_emails first to find the UID of the email you want to read. Args:
Returns: Full email with headers, body text, and attachment list. Does NOT return attachment binary data. Examples:
|
| proton_search_emailsA | Search emails in a folder using IMAP search criteria. Supports filtering by sender, recipient, subject, body text, date range, and read/flagged status. Returns email summaries — use proton_get_email to read the full content of a specific result. Args:
Returns: Paginated list of matching email summaries. Examples:
|
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 clear, distinct purpose: listing folders, listing emails, searching emails, and retrieving full email content. No overlap, even between list and search due to search's advanced filtering.
All tools follow a consistent 'proton_verb_noun' snake_case pattern (list_folders, list_emails, search_emails, get_email). No deviation in style or convention.
With 4 tools, the set is small but appropriate for a read-only email interface. It covers essential reading operations without unnecessary bloat, though some users might expect a few more common actions.
The tools cover the core read workflow (list folders, list/search emails, read full email) well, but completely lack write operations like send, delete, move, or mark as read. This is a notable gap for full email management.