WebMail / Private Office MCP

Your private office, open to Claude — on your terms.

WebMail / Private Office MCP connects Claude to the mailboxes and calendars you choose. It can read, search, file, draft and plan. It can never send a mail on its own, and any account can be kept strictly read-only.

Sign in ManualSupport

One person, one set of mailboxes

Every account you add belongs to you alone. Claude, working with your token, sees your accounts and nobody else's.

Nothing leaves without you

When Claude wants to send, the message is parked in your Drafts and shown in your Outbox. Only your click releases it.

Read-only, when you want

Flip an account to read-only and Claude can search and read but cannot move, flag, draft or send — not even mark a message as read.

Calendars too

Apple Calendar over CalDAV (and Fastmail, Google, Nextcloud) with full read-write, plus read-only ICS subscriptions. The same read-only switch applies.

Two-factor, always

Sign-in runs on Amazon Cognito: password plus an authenticator app, required for every account.

Every action on record

Sign-ins, tokens, connected apps and each tool call Claude makes are written to an activity log you can filter and export.

Credentials stay encrypted

Mail passwords are AES-256-GCM encrypted at rest and only ever used to reach your mail server. Tokens are stored hashed.

How it works

  1. Sign in — or use the sign-up link on the sign-in page if your address has been invited.
  2. Add a mailbox — Gmail, Outlook, Fastmail, iCloud, Yahoo or any IMAP server. Test it before Claude touches it.
  3. Connect Claude — a personal token for Claude Code, or one click for claude.ai and the desktop app.
  4. Ask — “what's new from the bank?”, “draft a reply to Anna”, “file last week's invoices”.
  5. Approve — anything Claude wants to send waits in your Outbox until you say so.

Security in short

Sign-up is limited to invited addresses. Accounts, passwords and MFA live in Amazon Cognito (12+ character policy, authenticator app required); the app never sees a password. Sessions are server-side, short-lived and bound to your browser. Personal tokens and OAuth grants are per user, revocable at any time and expire on their own. Failed sign-ins are rate-limited and trigger an alert to you. Every page carries a strict Content-Security-Policy. See Support for details and the operator contact.