Oryah Mail
Governed email and calendar for AI agents: per-mailbox permissions, a send allowlist, scoped keys, an audit log. A hosted remote MCP server that connects Gmail, Google Workspace, Microsoft 365 and IMAP mailboxes and calendars to Claude, Claude Code, Cursor and any Streamable HTTP client. Each mailbox has its own read, draft and send permissions, sends are limited to allowlisted domains, agents get scoped API keys with expiry, and every draft, send, change and refusal lands in an audit log.
What it is
A hosted remote MCP server that connects Gmail, Google Workspace, Microsoft 365 and IMAP mailboxes and calendars to Claude, Claude Code, Cursor and any Streamable HTTP client. Each mailbox has its own read, draft and send permissions, sends are limited to allowlisted domains, agents get scoped API keys with expiry, and every draft, send, change and refusal lands in an audit log.
Oryah Mail is an existing Infinihash product with its own site, sign-in and billing. The store lists it for completeness; details, documentation and support live at mail.infinihash.com and in the documentation.
The problem
An agent is only useful in email if it can act, and acting is where it does damage: a wrong recipient, a draft that got sent, a mailbox token sitting on the agent's disk. Most connectors give the agent the whole mailbox or nothing.
How it works
Connect a mailbox: Gmail, Google Workspace and Microsoft 365 by OAuth, anything else by IMAP app password. Tokens stay on the server; the agent never sees them.
Set Controls per mailbox: read, draft or send, and which domains sends may go to. To, Cc, Bcc and Reply-To are all checked.
Give each agent its own API key with a preset (read_only, read_draft or full) and an expiry. A key can never exceed the mailbox Controls.
Point Claude, Claude Code, Cursor or any Streamable HTTP MCP client at https://mail-mcp.infinihash.com/mcp: OAuth for people, a Bearer key for agents.
Read the audit log: every draft, send, change and refusal, with the key or session, the mailbox and the time. Revoke one key, or pause all of them, in one click.
For AI agents and the people who run them
- Remote MCP endpoint https://mail-mcp.infinihash.com/mcp (Streamable HTTP). OAuth with dynamic client registration for people; Authorization: Bearer omk_... for agents.
- 30 tools with readOnlyHint and destructiveHint (14 read, 9 write, 7 destructive); a key lists only the tools its scopes could allow. Send tools send immediately and say so.
- Key presets read_only, read_draft and full. Effective permission is the mailbox Controls AND the key scopes; audit rows carry the key name.
- A send to a domain outside the allowlist is denied and logged, including Bcc and Reply-To.
- Machine-readable index: https://mail.infinihash.com/llms.txt. Documentation: https://mail.infinihash.com/docs.html
- send_mail, reply, forward and send_draft accept idempotency_key: a retry returns the first result and never sends twice (kept 7 days). Keys can carry a daily send cap; the owner can pause every key at once.
What you get
- Gmail, Google Workspace, Microsoft 365 and IMAP mailboxes and calendars behind one connector
- Per-mailbox read, draft and send Controls
- Send-domain allowlist that also checks Bcc and Reply-To
- Scoped API keys for agents, with presets and expiry
- Audit log of every draft, send, change and refusal, included at every price
- Unified inbox and search across mailboxes; calendar read, create, update and free-time search
- OAuth tokens held server-side; the agent never receives mailbox credentials
- Daily send cap per key, one-button pause for all keys, and idempotency keys so a retried send never sends twice
- A key only advertises the tools it may use: a read-only key lists 13 of the 30 tools
Questions
- Which clients work?
- Claude web and desktop as a custom connector, Claude Code and Cursor through their remote MCP settings, and any client that speaks MCP over Streamable HTTP. People sign in with OAuth; agents use a Bearer API key.
- What can an agent key do?
- What its preset allows (read_only, read_draft or full) and never more than the mailbox Controls. Keys can expire and can be revoked at any time; every draft, send, change and refusal is logged under the key's name, and a key can carry a daily send cap.
- Can the agent email anyone?
- Only domains on the mailbox's send allowlist. Recipients in To, Cc, Bcc and Reply-To are all checked, and a denied send is logged.
- What does it cost?
- $1 per mailbox per month or $10 per mailbox per year, with a 14-day free trial; a card is required at checkout. Permissions, the allowlist, agent keys and the audit log are included. A Team plan at $15 per user per month is coming soon.
- What if my agent retries a send?
- Pass an idempotency_key on send_mail, reply, forward or send_draft. A repeated call with the same key returns the first result marked idempotent_replay and sends nothing; keys are honoured for 7 days. A send that was refused or failed releases its key so a corrected retry can go through.
What it does not do
- It is not an email address for agents: it connects mailboxes you already own.
- It does not widen access on its own: a key keeps its preset until the owner changes it.
- It is not self-hosted: Oryah Mail runs on AWS (us-east-2); the privacy page lists the subprocessors.
Pricing
$1 per mailbox per month or $10 per mailbox per year, with a 14-day free trial (card required at checkout). Permissions, the send allowlist, agent keys and the audit log are included on every mailbox. Team, $15 per user per month, is coming soon.
| Plan | Price |
|---|---|
| Per mailbox | $1 per mailbox/month or $10/year |
| Team (coming soon) | $15 per user/month, coming soon |