Proton Mail Mcp

Please install the `proton-mail-mcp` MCP server into my current AI client (that's you).

Required prerequisites (do these first if not already done):
- **Install Node.js 20 or newer** — Node.js 20+ is required to run the MCP server via npm/npx. (https://nodejs.org/)
- **Install and sign in to Proton Mail Bridge** — Proton Mail Bridge must be running on a machine you control. You must log in to your Proton account in Bridge and obtain the Bridge mailbox password from Account → Mailbox password. This is required because the server connects to Proton Mail through Bridge over IMAP/SMTP. (https://proton.me/mail/bridge)
- **Obtain Proton Bridge connection values** — You need your Proton email address, the Proton Mail Bridge mailbox password, and the sender address to use for outgoing mail.

Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","@alexendros/protonmail-mcp"]
- required environment variables:
  - `PROTON_BRIDGE_USER`: Proton account email address used by Proton Mail Bridge. (example: `<your-proton-email>`)
  - `PROTON_BRIDGE_PASS`: Mailbox password shown by Proton Mail Bridge; not your normal Proton account password. (example: `<your-bridge-password>`)
  - `PROTON_MAIL_FROM`: From address used for sending mail. The README indicates sending is fixed to the configured address. (example: `<your-proton-email>`)
  - `MCP_TRANSPORT`: Transport mode for the server. Use stdio for local MCP clients. (example: `stdio`)
- optional environment variables:
  - `PROTON_BRIDGE_TLS_INSECURE`: Set to true when connecting to a local Proton Mail Bridge with insecure/local TLS as shown in the README quickstart and Claude Code example. (example: `true`)
  - `LOG_LEVEL`: Logging verbosity for the server. (example: `<your-log-level>`)
  - `PROTON_BRIDGE_CA_PATH`: Optional CA certificate path for stricter Bridge TLS validation, mentioned in the roadmap as optional pinning support. (example: `<path-to-ca-certificate>`)

Note: The README documents both stdio and streamable HTTP transports. For the canonical install path, the simplest portable option is stdio via npx. HTTP deployment is also supported, but requires additional hosting and security configuration. For HTTP mode, the README indicates these additional env vars: MCP_AUTH_TOKEN (required), MCP_ALLOWED_ORIGINS (required in production), and likely MCP_TRANSPORT=http. No packaged remote URL is provided, so HTTP config is deployment-specific and omitted here.

Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.