{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/mailbox-access.connect-mailboxes/",
    "json": "https://www.anchorterminal.com/niches/mailbox-access.connect-mailboxes/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/mailbox-access.connect-mailboxes/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/mailbox-access.connect-mailboxes/index.min.md"
  },
  "markdown": "One company's docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 1 | 10 | 32 | 24 | 9 |\n\n## What counts as done\n\nEach 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.\n\nHow 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\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **Outlook Mail (Microsoft Graph) (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.\n\n## Does the job, with a limit\n\nIt 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.\n\n- **Aurinko Email API (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.\n- **CloudPost (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.\n- **email-agent-mcp (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.\n- **EmailEngine (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.\n- **Fastmail API (JMAP) (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.\n- **Gmail API (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.\n- **Himalaya (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.\n- **Nylas Email API (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).\n- **Unipile (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.\n- **Zoho Mail API (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.\n\n## What stops agents finishing\n\n- Gmail restricted scopes need an annual CASA assessment for a public app\n- OAuth registration that accepts only named clients' redirect URIs\n- IMAP and iCloud need an app-specific password handed to an intermediary\n- per-mailbox monthly price\n\n## Around it\n\nAfter: mailbox-access.find-and-read, mailbox-access.watch-new-mail.\n\n## Where this comes from\n\nWeight 24 of 100 in Mailbox access: 9 of 36 counted mentions (acc-05, 06, 13, 14, 16, 17, 25, 28, 34)\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/mailbox-access.connect-mailboxes.json, or the MCP tool get_use_case with id mailbox-access.connect-mailboxes. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Connect one or many people's mailboxes with the right access",
        "url": ""
      }
    ],
    "description": "Connect one or many people's mailboxes with the right access: 1 companies fully do it, 10 with a limit, 32 carry the tag. Every listing in Mailbox access with the reason and a source.",
    "facts": null,
    "h1": "Connect one or many people's mailboxes with the right access",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/mailbox-access.connect-mailboxes/",
    "published": "",
    "section": "agents",
    "title": "Connect one or many people's mailboxes with the right access | Anchor…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/mailbox-access.connect-mailboxes/"
  },
  "tokens": {
    "markdown": 1450,
    "slim": 380
  },
  "version": 1
}
