Proton Workflow Connector

Name: Proton Workflow Connector
Author: NtrpyDev

作者：NtrpyDev版本 1.3.0i★ –i在你的电脑上运行

注册名称io.github.NtrpyDev/proton-workflow-connector

安装

概览

作者提供的说明（英文原文）

Unofficial self-hosted MCP connector for Proton Mail Bridge and SimpleLogin.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i非常新↓ 12/周 · ★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他
你需要填写：PROTON_BRIDGE_USERNAME, PROTON_BRIDGE_PASSWORD, PROTON_BRIDGE_EMAIL, SIMPLELOGIN_API_KEY

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： PROTON_BRIDGE_USERNAME, PROTON_BRIDGE_PASSWORD, PROTON_BRIDGE_EMAIL, SIMPLELOGIN_API_KEY

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "proton-workflow-connector": {
      "command": "uvx",
      "args": [
        "proton-workflow-connector"
      ],
      "env": {
        "PROTON_BRIDGE_USERNAME": "your-value",
        "PROTON_BRIDGE_PASSWORD": "your-value",
        "PROTON_BRIDGE_EMAIL": "your-value",
        "SIMPLELOGIN_API_KEY": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add proton-workflow-connector --env PROTON_BRIDGE_USERNAME=your-value --env PROTON_BRIDGE_PASSWORD=your-value --env PROTON_BRIDGE_EMAIL=your-value --env SIMPLELOGIN_API_KEY=your-value -- uvx proton-workflow-connector

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "proton-workflow-connector": {
      "command": "uvx",
      "args": [
        "proton-workflow-connector"
      ],
      "env": {
        "PROTON_BRIDGE_USERNAME": "your-value",
        "PROTON_BRIDGE_PASSWORD": "your-value",
        "PROTON_BRIDGE_EMAIL": "your-value",
        "SIMPLELOGIN_API_KEY": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "proton-workflow-connector": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "proton-workflow-connector"
      ],
      "env": {
        "PROTON_BRIDGE_USERNAME": "your-value",
        "PROTON_BRIDGE_PASSWORD": "your-value",
        "PROTON_BRIDGE_EMAIL": "your-value",
        "SIMPLELOGIN_API_KEY": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

PROTON_BRIDGE_USERNAME 必填 env
Bridge IMAP/SMTP username (from the Bridge app)
PROTON_BRIDGE_PASSWORD 机密必填 env
Bridge-generated password (never your Proton account password)
PROTON_BRIDGE_EMAIL 必填 env
Primary Proton address served by Bridge
SIMPLELOGIN_API_KEY 机密 env
SimpleLogin API key; omit to disable alias tools

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 NtrpyDev 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 18475 个服务器的 0%
发布到注册中心的时间比此分类中其他 18475 个服务器的 13% 更新
基础检查结果等于或优于此分类中其他 18475 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Proton Workflow Connector 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：PROTON_BRIDGE_USERNAME, PROTON_BRIDGE_PASSWORD, PROTON_BRIDGE_EMAIL, SIMPLELOGIN_API_KEY

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.3.0）于4个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, Tethered Trust

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

作者：formulahendry起步阶段↓ 66/周★ 44014个月前更新

在你的电脑上运行

安装

Remote Desktop Commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

作者：desktop-commander正在增长★ 2113天前更新

在云端运行✓ desktopcommander.app

安装

Tethered Trust

Fit, compatibility and recall checks for AI agents before they buy: verdicts, evidence, receipts.

作者：tetheredtrust.com非常新今天更新

在云端运行✓ tetheredtrust.com

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Proton Workflow Connector

Proton Workflow Connector (PWC) is a self-hosted MCP connector for reading, sending, organizing, and automating Proton Mail through Proton Mail Bridge. It works with any MCP client or local agent runtime that can launch a stdio server or call a Streamable HTTP MCP endpoint. SimpleLogin support is optional.

This is an unofficial project. It is not affiliated with, endorsed by, or sponsored by Proton AG. The connector uses Bridge-generated IMAP/SMTP credentials. It does not accept Proton account passwords or store Proton login sessions.

Quick start · Example workflows · Capabilities · Automations · Security · Documentation · Buy Me a Coffee

Why use it?

Use one local server for the mail work agents usually have to piece together:

Search, read, send, reply, forward, draft, label, archive, and download attachments through 53 Proton Mail tools.
Require confirmation for destructive tools, preview sends and destructive operations with dry_run, sanitize outbound HTML by default, bound bulk operations, and allow only configured sender addresses.
React to new mail or SimpleLogin aliases through MCP polling or a background watcher that can call a webhook, append JSONL, or run a command.
Add 13 SimpleLogin tools when you want alias, contact, and mailbox management.
Connect over stdio, localhost Streamable HTTP, or OAuth-protected hosted HTTP.

The server exposes 68 tools in total. See the complete tool reference.

How it works

PWC is an MCP server. Your client starts it over stdio or connects to it over Streamable HTTP.

The connector talks to Proton Mail Bridge over local IMAP/SMTP. Bridge must be installed, signed in, and running on the same machine as the connector. One connector process serves one Bridge account.

SimpleLogin is optional. If SIMPLELOGIN_API_KEY is set, PWC adds alias, contact, mailbox, and new-alias polling tools. If it is unset, the Proton Mail tools still work.

For automation, run proton-workflow-watch or call the polling tools from your MCP client. Watcher output can go to a webhook, a JSONL file, or a command.

Quick start

Prerequisites

Python 3.11 or newer
Proton Mail Bridge, signed in and running
The IMAP/SMTP host, ports, username, and generated password shown by Bridge
A SimpleLogin API key only if you want the optional SimpleLogin tools

1. Install

git clone https://github.com/NtrpyDev/proton-workflow-connector.git

cd proton-workflow-connector python -m venv .venv source .venv/bin/activate python -m pip install .

On Windows PowerShell, activate the environment with .venv\Scripts\Activate.ps1.

2. Configure Bridge credentials

Keep the environment file outside the repository:

mkdir -p ~/.config/proton-workflow-connector

cp .env.example ~/.config/proton-workflow-connector/env chmod 600 ~/.config/proton-workflow-connector/env

Edit the copied file with the connection details shown in Proton Mail Bridge. Set PROTON_BRIDGE_EMAIL to the default sender and list every permitted sender address in PROTON_BRIDGE_SENDER_ADDRESSES.

3. Run the connector

proton-workflow-connector --transport stdio \

--env-file ~/.config/proton-workflow-connector/env

4. Connect an MCP client

Any MCP client or local agent runtime can use PWC as long as it supports stdio or Streamable HTTP:

stdio: run proton-workflow-connector --transport stdio --env-file ...
HTTP: run the connector with --transport streamable-http and point the client at /mcp

Claude Code stdio example:

claude mcp add --transport stdio --scope user proton-workflow \

-- "$PWD/.venv/bin/proton-workflow-connector" --transport stdio \ --env-file ~/.config/proton-workflow-connector/env

Codex stdio example:

[mcp_servers.proton_workflow]

command = "/absolute/path/to/repo/.venv/bin/proton-workflow-connector" args = [ "--transport", "stdio", "--env-file", "/absolute/path/to/private/proton-workflow-connector-env" ] default_tools_approval_mode = "prompt" startup_timeout_sec = 20 tool_timeout_sec = 120

Run server_status after connecting. It checks IMAP, SMTP, SimpleLogin, OAuth configuration, and the server version without returning secrets. Then run list_folders; Bridge folder names vary by account and version.

See MCP client setup for generic client configuration, localhost HTTP, hosted Streamable HTTP, Codex, Claude Code, and the plugin wrapper.

Example workflows

Once connected, ask your MCP client to:

"List my mail folders and show the unread count for each."
"Find unread invoices from the last 30 days without marking them read."
"Draft a reply to the latest message in this thread, but do not send it."
"Download the PDF attachments from this message."
"Archive these message UIDs after showing me the exact list."
"Create a SimpleLogin alias for shopping and add a contact for this merchant."
"Poll for new mail from billing@vendor.example using the invoices cursor."

The connector returns structured data to the MCP client. The client decides how to present it and when to request approval for actions.

Capabilities

Area	Included operations
Search and reading	Search one folder or all selectable folders, read messages and threads, inspect headers, and download attachments
Sending and drafts	Send, reply, reply-all, forward, create and update drafts, use allowed alternate senders, and attach files
Organization	Create and manage folders, apply Proton labels, change flags, archive, move, copy, restore, and manage Spam or Trash
Bounded bulk actions	Preview, mark, star, move, copy, archive, trash, restore, or permanently delete explicit UID lists
Automations	Poll persistent cursors or push new-message and new-alias events to a webhook, JSONL file, or command
SimpleLogin	Inspect account data and manage aliases, contacts, and mailboxes with an optional API key
Deployment	Local stdio, localhost Streamable HTTP, or OAuth/OIDC-protected hosted HTTP

Proton Contacts are not included because Proton Mail Bridge does not expose them.

Automations

The background watcher polls for new mail or newly created SimpleLogin aliases and emits one event per new item:

proton-workflow-watch \

--env-file ~/.config/proton-workflow-connector/env \ --folder INBOX \ --webhook-url https://example.com/hooks/proton \ --interval 60

Key behavior:

The first run establishes a baseline and does not replay the existing mailbox.
Persistent cursors survive restarts and account for IMAP UIDVALIDITY changes.
Webhook delivery is at-least-once, with retries, exponential backoff, and dead-letter handling.
An optional HMAC-SHA256 signature lets webhook receivers verify each event.
Events contain message metadata only; bodies and attachments remain available on demand through MCP tools.
JSON rules can run several independently filtered triggers from one watcher.
--dry-run shows which events and rule actions would fire without delivering, acting, or advancing cursors.

Read Triggers and webhooks for event schemas, filters, delivery guarantees, signature verification, rules, and systemd examples.

Security model

This connector processes private mail. Its defaults and boundaries are intentionally explicit:

Prefer local stdio. Bridge and the connector should stay on the same trusted machine whenever possible.
Keep credentials private. Store Bridge-generated credentials and optional API keys outside Git with user-only permissions.
Confirm destructive actions. Permanent deletion, empty-folder operations, folder deletion, and alias deletion require confirm=true after explicit user intent.
Preview before mutating. Sends, forwards, replies, bulk actions, permanent delete, and empty-folder operations support dry_run=true previews.
Treat mail as untrusted. Read/search results mark email content as content_trust: "untrusted", and outbound HTML is sanitized unless trusted_html=true.
Bound bulk operations. Bulk tools require explicit numeric UIDs and default to a maximum of 50 messages per call.
Restrict senders. Mail can only be sent from PROTON_BRIDGE_EMAIL or an address in PROTON_BRIDGE_SENDER_ADDRESSES.
Protect remote access. Non-local HTTP deployments require deliberate Host/Origin policy; internet deployments require HTTPS and an external OAuth/OIDC provider.
Limit exposed data. Optional audit records exclude addresses, message bodies, attachments, credentials, and tokens.
Treat events as untrusted input. Email subjects and alias names can be attacker-controlled; webhook receivers and commands must validate event fields.

Read SECURITY.md before using real mail and Hosted HTTP setup before exposing the connector beyond localhost.

Known boundaries

Proton Mail Bridge must remain running while the connector or watcher is active.
One server process connects to one Bridge account.
Proton Contacts, native scheduled sending, filters, account settings, and key management are not exposed by Bridge and are not emulated.
New-mail and new-alias triggers use polling because Proton and SimpleLogin do not provide a compatible push API.
Trigger events include metadata, not message bodies or attachments.
All Mail is a virtual read-only Bridge mailbox; start move and permanent-delete operations from a writable folder.

Documentation

Guide	Use it for
Setup	Bridge configuration, private environment files, folder names, and network modes
Tool reference	All 68 MCP tools, arguments, safety limits, and boundaries
Client setup	Generic MCP clients, local agents, Codex, Claude Code, plugins, and Streamable HTTP
Triggers and webhooks	Watcher rules, payloads, delivery behavior, and signature verification
Hosted HTTP	OAuth/OIDC, HTTPS, Host/Origin validation, scopes, audit logs, and systemd
Integration tests	Live Bridge and SimpleLogin verification

Official upstream references:

Development

Install the development dependencies and run the local checks:

python -m pip install -e ".[dev]"

ruff check . ruff format --check . pytest python -m compileall -q src pip-audit gitleaks detect --redact --config .gitleaks.toml

Tests use synthetic data and do not require access to a real mailbox. Live checks are documented separately in Integration tests.

See CONTRIBUTING.md for contribution and privacy requirements. Report security issues privately as described in SECURITY.md.

License

MIT. See LICENSE.

Proton Workflow Connector

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

需要你填写的值

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“其他”中的其他服务器比较i

常见问题

替代选择

Spec Driven Development

Remote Desktop Commander

Tethered Trust

作者的 README

Proton Workflow Connector

Why use it?

How it works

Quick start

Prerequisites

1. Install

2. Configure Bridge credentials

3. Run the connector

4. Connect an MCP client

Example workflows

Capabilities

Automations

Security model

Known boundaries

Documentation

Development

License