Connect one or many people's mailboxes with the right access
One company's docs show a full fit.
What counts as done
Each mailbox connects through the provider's consent screen with only the requested level (read, draft or send), the agent can name which mailbox each call acts on, and no user can reach another's mail.
How agents ask for it: connect my work and personal Gmail
, let each of our users connect their Outlook
, give the agent read-only access to my mail
Does the job 1
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Outlook Mail (Microsoft Graph) C Microsoft Corporation | Delegated permissions separate Mail.ReadBasic, Mail.Read, Mail.ReadWrite and Mail.Send on the Entra consent screen, each call names the mailbox through /me or /users/{id}, and a delegated token reaches only the signed-in user's mail. source |
Does the job, with a limit 10
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| Aurinko Email API F Yoxel, Inc. | Each user connects through the provider's OAuth via Aurinko and calls act on that account's token, but the listing notes say the app's client ID and secret reach every connected mailbox and IMAP accounts hand Aurinko a password; scope choices weren't reopened. source |
| CloudPost F CloudPost (James Brooks) | Mailboxes connect by IMAP and SMTP credentials such as an Apple app-specific password handed to CloudPost, not a provider consent screen, and the OAuth metadata has one scope, mcp:use, so a client can't be limited to reading. source |
| email-agent-mcp B UseJunior | The observe profile requests only Mail.Read and write tools need a mailbox named when several are configured, but the README says switching full to observe keeps the old token's write scopes, Gmail sign-in goes through a UseJunior broker, and there is no draft-only level. source |
| EmailEngine BB Postal Systems OÜ, Narva mnt 5, 10117 Tallinn, Estonia, registry code 14971894 | Tokens bind to one account with a permissions record and MCP mail levels run from none through read-only to mail agent, enforced by the REST layer, but the operator registers each provider's OAuth app, so Gmail's restricted-scope review still applies, and pre-2.84.2 bound tokens could reach other accounts. source |
| Fastmail API (JMAP) C Fastmail Pty Ltd, ACN 142 646 580, PO Box 234, Collins Street West, VIC 8007, Australia | OAuth separates jmap:mail from jmap:submission, and the MCP consent screen has read-only, write and send (acc-06), but jmap:mail has no read-only form, public redirect URIs need manual registration through partnerships, and acc-05 found the MCP accepting only claude.com, chatgpt.com and localhost. source |
| Gmail API A Google LLC | OAuth scopes split reading (gmail.readonly), drafting (gmail.compose) and sending (gmail.send), but every reading scope is restricted, so a public app needs verification and an annual CASA assessment (acc-13, acc-14), and compose also sends. source |
| Himalaya C No legal entity found. Copyright Clément DOUIN (soywod) | Accounts are named in the TOML config and the MCP server is read-only unless --allow-write or --allow-send is passed, but that limit is tool hiding, not a provider scope, Gmail and Fastmail over IMAP need app passwords, and the MCP server serves one account. source |
| Nylas Email API A Nylas, Inc. | Each mailbox is a grant reached by /v3/grants/{grant_id}, so every call names its mailbox, and the spec lists minimum provider scopes per operation, but the application API key reaches every grant, and IMAP and iCloud need app passwords handed to Nylas (acc-34). source |
| Unipile B UNIPILE SAS | Every mail call takes an account_id, so the agent names the mailbox, but the listing notes say a v1 access token reaches every connected account, with scoped keys only in the v2 beta, and IMAP accounts hand Unipile a password; consent levels weren't documented on the pages read. source |
| Zoho Mail API D Zoho Corporation Private Limited | OAuth scopes split READ, CREATE, UPDATE and DELETE on ZohoMail.messages and every call names an accountId, but drafting and sending share ZohoMail.messages CREATE, so a drafting grant can also send. source |
What stops agents finishing
- Gmail restricted scopes need an annual CASA assessment for a public app
- OAuth registration that accepts only named clients' redirect URIs
- IMAP and iCloud need an app-specific password handed to an intermediary
- per-mailbox monthly price
Around it
After: mailbox-access.find-and-read, mailbox-access.watch-new-mail.
Where this comes from
Weight 24 of 100 in Mailbox access: 9 of 36 counted mentions (acc-05, 06, 13, 14, 16, 17, 25, 28, 34)
The same as data: /api/v1/use-cases/mailbox-access.connect-mailboxes.json, or the MCP tool get_use_case with id mailbox-access.connect-mailboxes. Other jobs in this category: /api/v1/niches?category=mailbox-access.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.