io.github.sethbang/proton-mail-mcp

npm

Unofficial Proton Mail MCP — send, read, search & organize email over SMTP and IMAP

2 14.9M/wk 29 tools GitHub npm

No known CVEs

No license

Actively maintained

Last commit 5d ago

Works with most clients

Transport: stdio, sse, http

29 tools · ~2.6k tok

Grade C · 1.3% of 200K ctx

Edit this pageView history

Communication

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, sse, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "protonmail": {
      "env": {
        "PROTONMAIL_PASSWORD": "your-smtp-password",
        "PROTONMAIL_USERNAME": "your-email@protonmail.com"
      },
      "args": [
        "-y",
        "proton-mail-mcp"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-sethbang-proton-mail-mcp)](https://mcppedia.org/s/io-github-sethbang-proton-mail-mcp)

Read me

What io.github.sethbang/proton-mail-mcp does

A Model Context Protocol (MCP) server that gives AI assistants full access to your Proton Mail account -- send, read, search, and organize email over SMTP and IMAP.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

83/100across 5 weighted dimensions

How we score →

0255075100

−17

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

8 fixed

CVE-2022-29244high · fixedCVSS 7.5

Packing does not respect root-level ignore files in workspaces

### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up

Affected: >= 7.9.0Fixed in 8.11.0source →

CVE-2018-7408high · fixedCVSS 7.8

Incorrect Permission Assignment for Critical Resource in NPM

An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.

Affected: >= 0Fixed in 5.7.1source →

CVE-2013-4116info · fixed

Local Privilege Escalation in npm

Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.

Affected: >= 0Fixed in 1.3.3source →

CVE-2020-15095medium · fixedCVSS 4.4

npm CLI exposing sensitive information through logs

Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.

Affected: >= 0Fixed in 6.14.6source →

CVE-2019-16777high · fixedCVSS 7.7

npm Vulnerable to Global node_modules Binary Overwrite

Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b

Affected: >= 0Fixed in 6.13.4source →

Inventory

Tools (29)

Click any tool to inspect its schema.

~2.6k tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.sethbang/proton-mail-mcp safe to use?: io.github.sethbang/proton-mail-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.sethbang/proton-mail-mcp?: io.github.sethbang/proton-mail-mcp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can io.github.sethbang/proton-mail-mcp do?: io.github.sethbang/proton-mail-mcp provides 29 tools: send_email, reply_email, reply_all_email, forward_email, save_draft and 24 more. See the full tools list on the server page for descriptions and parameters.
What AI clients work with io.github.sethbang/proton-mail-mcp?: io.github.sethbang/proton-mail-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.
Is io.github.sethbang/proton-mail-mcp actively maintained?: io.github.sethbang/proton-mail-mcp is actively maintained — last commit was 5 days ago. It has 2 GitHub stars.

Similar servers

Others in communication

View all →

Mcp_agent_mail96

Asynchronous coordination layer for AI coding agents: identities, inboxes, searchable threads, and advisory file leases over FastMCP + Git + SQLite

2.0k 6

Ms 365 Mcp Server91

A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API

803 22

Server90

PubNub Model Context Protocol MCP Server for Cursor and Claude

31 2

Teams.Mcp90

<p> <a href="https://www.npmjs.com/package/@microsoft/teams.mcp" target="_blank"> <img src="https://img.shields.io/npm/v/@microsoft/teams.mcp/latest" /> </a> <a href="https://www.npmjs.com/package/@microsoft/teams.mcp?activeTab=code" t

100 8

MCP Security Weekly

Get CVE alerts and security updates for io.github.sethbang/proton-mail-mcp and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

{ "mcpServers": { "protonmail": { "env": { "PROTONMAIL_PASSWORD": "your-smtp-password", "PROTONMAIL_USERNAME": "your-email@protonmail.com" }, "args": [ "-y", "proton-mail-mcp" ], "command": "npx" } } }

Proton Mail MCP Server

A Model Context Protocol (MCP) server that gives AI assistants full access to your Proton Mail account -- send, read, search, and organize email over SMTP and IMAP.

⚠️ Unofficial — not affiliated with Proton. This is an independent, community-built project. It is not developed, endorsed, sponsored, or supported by Proton AG. "Proton", "Proton Mail", and "Proton Mail Bridge" are trademarks of Proton AG, used here only to describe interoperability. It talks to Proton Mail over the standard SMTP submission endpoint and the locally-run Proton Mail Bridge; no Proton private API is used. Use at your own risk.

Features

Send, reply, and forward email via Proton Mail SMTP with threading headers; dedicated reply_all_email tool

Markdown bodies -- pass markdownBody to send_email / reply_email / reply_all_email / forward_email; rendered to HTML with a plain-text fallback

Read email via IMAP through Proton Mail Bridge

Attachments -- send files (base64), download to memory or to disk (saveTo + ALLOW_FILE_DOWNLOAD_DIR), forward a subset by part number

Search messages by sender, recipient, subject, body, date, flags, size, List-ID, attachment presence, attachment name (substring), and attachment MIME type

Organize -- move, delete, and flag/unflag messages individually or in bulk; bulk-update labels too

Bulk operations -- bulk_move, bulk_delete, bulk_update_flags, bulk_update_labels with dryRun preview and XOR uid/match input

Folder & label management -- create_folder, create_label, rename_folder, delete_folder (non-destructive on Proton); empty_folder (opt-in via ALLOW_EMPTY_FOLDER=true; not recommended)

Labeling -- update_message_labels adds and removes Proton labels on a message (additive — message stays in its source folder)

Aggregations -- count_messages, folder_stats, top_senders (with excludeSelf + per-row direction) for inbox analytics

Thread mutations -- move_thread, delete_thread, flag_thread with optional cross-folder walk; get_thread dedupes by Message-ID across mailbox copies

Snippets -- optional includeSnippet on list_messages and search_messages for at-a-glance previews

List folders with message and unread counts

Honest accounting -- post-STORE FETCH verify on flags/labels surfaces silently-dropped operations as notApplied; sent-copy lookup retries SEARCH to defeat Proton's index lag; Reply-To rewrites are surfaced in the send response

Safety first -- delete moves to Trash by default (via special-use resolver), read-only mode via READONLY=true, dryRun on all bulk ops, MCP tool annotations for client-side confirmation prompts, path-traversal defense on filesystem-touching tools

Security hardened -- input validation, credential sanitization, rate limiting, attachment size limits

Works with any MCP-compatible client (Claude Desktop, Claude Code, Cursor, etc.)

Frequently Asked Questions

Is io.github.sethbang/proton-mail-mcp safe to use?

io.github.sethbang/proton-mail-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install io.github.sethbang/proton-mail-mcp?

io.github.sethbang/proton-mail-mcp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What can io.github.sethbang/proton-mail-mcp do?

io.github.sethbang/proton-mail-mcp provides 29 tools: send_email, reply_email, reply_all_email, forward_email, save_draft and 24 more. See the full tools list on the server page for descriptions and parameters.

What AI clients work with io.github.sethbang/proton-mail-mcp?

io.github.sethbang/proton-mail-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.

Is io.github.sethbang/proton-mail-mcp actively maintained?

io.github.sethbang/proton-mail-mcp is actively maintained — last commit was 5 days ago. It has 2 GitHub stars.