Email and calendar
Proton Mail for AI agents.
Managed auth, ready-made tools.
Search, read, send and file Proton Mail messages on behalf of each of your users.
About Proton Mail
With the Proton Mail connector, your agent works with the mailbox of each user who connects their Proton account. It can search and read mail, send a message and file messages into folders, using only the tools your project allows.
Proton Mail is an end-to-end encrypted email service from Proton, based in Switzerland.
Tools
What your agent can do in Proton Mail.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Proton Mail connection.
-
Search mail
Readproton_mail_searchFind messages by sender, subject or date.
-
Get a message
Readproton_mail_get_messageRead a message with its headers and body.
-
Send email
Writeproton_mail_sendSend a new message or a reply.
-
Move a message
Writeproton_mail_move_messageMove a message to a folder or label.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Proton Mail, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let the agent search and read, and switch off
proton_mail_sendif it should never send mail. -
Restrict what the agent reaches
Choose the endpoints a project may use. A call outside them is refused.
Get started
Connect Proton Mail
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect Proton Mail
Each end user authorizes their own Proton Mail account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own Proton Mail account, once. const connection = await agent200 .user("user_123") .connect("proton_mail"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the Proton Mail tools
Name the user, the model and the tools. The model decides which Proton Mail tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "Any new email from my accountant this week?", tools: ["proton_mail"], }); console.log(result.output);
Access
Sign-in and permissions.
-
How a user connects
Proton Mail offers no OAuth for other apps. Mail apps connect through Proton Mail Bridge, which the user runs on their own computer and which issues its own password; their Proton password is never shared.
-
What the connection can reach
The mailbox of the Proton account signed in to Bridge. Proton Mail Bridge is available on paid Proton plans.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Proton Mail connector and how to use it.
Connector: Proton Mail, through Agent200. In code: "proton_mail". What it does: Search, read, send and file Proton Mail messages on behalf of each of your users. Page: https://www.agent200.com/tools/proton-mail/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on Proton Mail's own page, through the authorization link Agent200 returns. Never ask a user for a Proton Mail password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: proton_mail_search, proton_mail_get_message. Write tools: proton_mail_send, proton_mail_move_message. Name "proton_mail" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/tools/proton-mail/framework/claude/ https://www.agent200.com/tools/proton-mail/framework/chatgpt/ https://www.agent200.com/tools/proton-mail/framework/claude-code/ https://www.agent200.com/tools/proton-mail/framework/muse/ https://www.agent200.com/tools/proton-mail/framework/grok-bot/ https://www.agent200.com/tools/proton-mail/framework/openai-dots/ https://www.agent200.com/tools/proton-mail/framework/claude-duet/ https://www.agent200.com/tools/proton-mail/framework/hermes-agent/ https://www.agent200.com/tools/proton-mail/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /tools/proton-mail.md
Guides
Use Proton Mail with the AI you build on.
Step-by-step setup for Proton Mail with a specific model, assistant or agent framework.
-
Proton Mail + Claude
How to connect Proton Mail to Claude
-
Proton Mail + ChatGPT
How to connect Proton Mail to ChatGPT
-
Proton Mail + Claude Code
How to connect Proton Mail to Claude Code
-
Proton Mail + Muse
How to connect Proton Mail to Muse
-
Proton Mail + Grok Bot
How to connect Proton Mail to Grok Bot
-
Proton Mail + OpenAI Dots
How to connect Proton Mail to OpenAI Dots
-
Proton Mail + Claude Duet
How to connect Proton Mail to Claude Duet
-
Proton Mail + Hermes Agent
How to connect Proton Mail to Hermes Agent
-
Proton Mail + OpenClaw
How to connect Proton Mail to OpenClaw
FAQ
Proton Mail and Agent200, answered.
Who handles the Proton Mail OAuth flow and the tokens?
Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Proton Mail.
Does my agent act as the end user?
Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Proton Mail connection, never another user's. It cannot reach anything the user or Proton Mail has not authorized.
Can I limit what my agent can do in Proton Mail?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.