Proton Workflow Connector MCP Server

What the code does

We read the source, 1 h ago · rules 3dff92dd89df

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    proc = subprocess.run(list(argv), input=body, capture_output=True, timeout=timeout)  # noqa: S603

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add proton-workflow-connector -- uvx proton-workflow-connector

{
  "mcpServers": {
    "proton-workflow-connector": {
      "args": [
        "proton-workflow-connector"
      ],
      "command": "uvx"
    }
  }
}

[mcp_servers.proton-workflow-connector]
command = "uvx"
args = ["proton-workflow-connector"]

{
  "mcpServers": {
    "proton-workflow-connector": {
      "args": [
        "proton-workflow-connector"
      ],
      "command": "uvx"
    }
  }
}

{
  "mcpServers": {
    "proton-workflow-connector": {
      "args": [
        "proton-workflow-connector"
      ],
      "command": "uvx"
    }
  }
}

This one needs environment variables set before it will start: PROTON_BRIDGE_USERNAME (Bridge IMAP/SMTP username (from the Bridge app)), PROTON_BRIDGE_PASSWORD (Bridge-generated password (never your Proton account password)), PROTON_BRIDGE_EMAIL (Primary Proton address served by Bridge), SIMPLELOGIN_API_KEY (SimpleLogin API key; omit to disable alias tools). The author declared them in the registry entry; get the values from the project itself.