Please add official MCP support for Proton Mail and Proton Calendar via remote streamable HTTP.

This is becoming essential for anyone who uses AI agents for serious personal or professional work. I need trusted agents—whether Claude Enterprise with strong contractual protections today, or hopefully Lumo through MCP in the future—to be able to securely see, manage, search, summarize, and draft emails and calendar events on my behalf.

For professionals and business customers, email and calendar are not side features. They are the operating system of work. If agents cannot access them, they cannot actually help with the workflows people pay for: preparing for meetings, tracking commitments, drafting replies, triaging inboxes, scheduling, following up, and coordinating across projects.

Proton is well positioned to do this the right way: privacy-preserving, user-authorized, auditable, revocable, and scoped. MCP is a natural fit because it allows Proton to expose controlled capabilities without forcing users into unsafe scraping, unofficial bridges, browser hacks, or full-account access through less trustworthy tools.

This is not just a power-user request. Business customers and professionals are increasingly going to expect their core productivity stack to work with agents. If Proton Mail and Calendar cannot participate in that ecosystem, Proton becomes harder to choose for serious work, even for people who strongly prefer Proton’s privacy model.

Please support Proton Mail and Calendar as official MCP servers using remote streamable HTTP, with granular permissions for reading, searching, labeling, drafting, sending, calendar lookup, event creation, and event updates.