Server facts
proton-mail-mcp
Project
- Author
- sethbang
- Repository
- github.com/sethbang/proton-mail-mcp
- License
- Not specified
- Category
- Communication
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 7
- Last commit
- Data as of
Overview
Email composition and mailbox maintenance sit alongside each other in proton-mail-mcp. Assistants can prepare drafts, send Markdown content, reply to individual senders or all recipients, and forward messages with selected attachments. Reading and search use IMAP through a locally running Proton Mail Bridge, while outgoing messages use SMTP. Search filters cover message content, dates, flags, and attachment properties. Attachment tools separate metadata inspection from retrieval, returning encoded content or saving files within a configured directory. The project is independent of Proton AG and does not use Proton’s private API.
Organization tools handle folders, additive labels, message flags, and moves or deletions across selected messages or reply threads. Bulk actions accept explicit message identifiers or search criteria and offer previews before changes. Deletion normally sends mail to Trash, and a read-only setting is available. Counts, folder statistics, and sender-frequency reports support mailbox analysis, although cached folder-list counts can be stale. Thread lookup follows reply headers rather than collecting forwarded copies. Send responses distinguish SMTP acceptance from a verified Sent-folder copy, and flag or label updates report changes the server did not apply.
proton-mail-mcp setup notes
- proton-mail-mcp records stdio only; confirm a network transport upstream before planning remote access.
- proton-mail-mcp has no recorded license; confirm reuse terms in its repository.