One agent across every Gmail inbox you have.

Your email doesn’t live in one account. Between your work address, a shared support@ or founders@ inbox, and your personal Gmail, your day is spread across two or three mailboxes. Standard AI connectors only sign into one Google account at a time. comail puts all of your inboxes behind a single MCP URL, with separate visibility rules for each account, so one assistant can help across them without reading too much or replying from the wrong address.

Takes a minute to apply. No credit card required.

chief-of-staff1 MCP URL · 3 inboxes attached

you@company.com · Google Workspace

Only investor & labeled threads shared

  • Sequoia: Partner meeting Thursday — matched by @sequoiacap.com rule
  • Q3 hiring plan — shared via co:chief-of-staff
  • Rest of work inbox — invisible by default

allow-list modedefault deny

support@company.com · shared team inbox

Full customer queue visible, minus pulled-back threads

  • Dana Ortiz: CSV export fails on large workspaces — visible
  • Confidential thread — withheld with no:chief-of-staff

deny-list modedefault allow

you@gmail.com · personal Gmail

Paused for the weekend

  • Access paused — comail makes zero calls to Google until you resume

allow-list modepaused

One MCP connection in your client, three different postures in Gmail: a tight allow-list at work, the full queue on support@, and your personal Gmail paused whenever you’re off the clock.

The problem

Your AI connector lives in one Gmail account. Your day happens in three.

Asking an assistant “what needs my attention today?” only works if it can look where your mail actually lands. With standard Gmail integrations, you’re stuck logging in and out of one account at a time, or duct-taping multiple MCP servers together.

01

Built-in connectors are single-account

Claude and ChatGPT only let you connect one Google account at a time. Checking a shared support@ inbox or grabbing a travel confirmation from your personal Gmail means disconnecting your work account and signing in all over again.

02

Stacking MCP servers confuses the model

Wiring up separate MCP servers for gmail-work, gmail-support, and gmail-personal triples the tool definitions in your context window and leaves the model guessing which server’s search_threads or send_message tool to call.

03

Different inboxes need different boundaries

You might want an agent reading every ticket in support@, only the threads you hand it in your work inbox, and almost nothing in your personal Gmail. Raw OAuth gives the model the exact same all-or-nothing grant everywhere.

How it works

One MCP URL on the outside. Separate rules for each inbox underneath.

  1. Connect your Google accounts in comail

    Sign in to each personal Gmail or Google Workspace account once from the comail dashboard. Each account is authorized independently, and your Google OAuth tokens stay with comail rather than sitting on your laptop or inside your AI client.

  2. Attach them to a single agent

    Create an agent like chief-of-staff and attach your work, support@, and personal inboxes. You get one MCP URL to add to Claude, ChatGPT, Cursor, or OpenClaw.

  3. Set the visibility rules per inbox

    Give each inbox the posture that fits it. Keep your work inbox on an allow-list (default: deny) so the agent only sees threads labeled co:chief-of-staff, while letting it read all of support@ except threads you tag no:chief-of-staff.

  4. Search and reply across accounts without mixups

    Your agent calls list_mailboxes to see which accounts are active, then passes the target mailbox address on every tool call. When it drafts or sends a reply, it stays inside that inbox and replies from the address the thread was sent to.

chief-of-staff — claude

> What needs my attention this morning across my inboxes?

comail · list_mailboxes

you@company.com (active) · support@company.com (active) · you@gmail.com (paused)

comail · search_threads (mailbox: "you@company.com", query: "is:unread")

thr_4c10: Sequoia — “Partner meeting: Thursday 10 AM”

Only threads labeled co:chief-of-staff are searched

comail · search_threads (mailbox: "support@company.com", query: "is:unread")

thr_9e27: Dana Ortiz — “CSV export fails on large workspaces”

you@gmail.com is paused; not searched

Two threads need you: Sequoia’s Thursday partner meeting in you@company.com, and Dana Ortiz’s CSV export bug report in support@company.com.

One prompt, one MCP server. The agent checks each active inbox under that account’s rules and skips your paused personal Gmail.
chief-of-staff — claude

> Draft a reply to Dana letting her know the fix is live.

comail · create_draft (thread_id: "thr_9e27")

mailbox required: this agent reaches several mailboxes; pass mailbox with one of the addresses listed by list_mailboxes

comail · create_draft (mailbox: "support@company.com", thread_id: "thr_9e27", body: "Hi Dana — we just shipped a fix…")

draft_id: "d-5512" · from support@company.com · saved in Gmail Drafts

Saved a reply to Dana in support@company.com’s Drafts for you to review.

If a tool call omits the target inbox, comail refuses to guess. The reply is saved in support@company.com’s Drafts and goes out from support@, with that account’s signature.

Configuration

Different rules for every inbox, behind one URL.

Each inbox attached to an agent has its own default policy, its own co: and no: labels, its own auto-labeling rules, and its own pause switch.

chief-of-staff access across a work inbox, a shared support inbox, and a personal Gmail
InboxWhat chief-of-staff seesDefaultAccess
you@company.com Only threads labeled co:chief-of-staff (by hand in Gmail or via a rule for @sequoiacap.com) deny active
support@company.com Every thread in the inbox, except those labeled no:chief-of-staff allow active
you@gmail.com Only threads labeled co:chief-of-staff deny paused
01

Strict per-inbox isolation

Every tool call requires an explicit mailbox address, and thread, message, and draft IDs only resolve inside the inbox they came from. An agent can never accidentally apply a label or send a draft against the wrong account.

02

Replies always use the right sender

Replies go out from the address the original thread was sent to, matching Gmail’s own Reply button and using that account’s signature. A ticket on support@ is never answered from your personal Gmail.

03

Pause one inbox without touching the rest

Flip any inbox to paused in the dashboard and comail stops calling Google for that account immediately. Your other inboxes keep working, and your labels, rules, and client sign-in are waiting when you unpause.

Want a work agent to see almost nothing in your personal Gmail? See keeping your personal life out of your job’s LLMs, or the multi-inbox feature table.

FAQ

Common questions.

Can I mix personal Gmail and Google Workspace accounts?

Yes. You can attach any combination of personal @gmail.com addresses, Google Workspace accounts from different domains, and shared team inboxes like support@ or founders@. Each one connects with its own Google sign-in.

Can an agent search all of my inboxes in a single API call?

No, by design. Each search runs inside one inbox under that inbox’s visibility rules, and the agent combines the results in your conversation. Keeping calls scoped to one mailbox at a time prevents thread or draft IDs from ever crossing accounts.

Can I let an agent send emails from support@, but only save drafts in my work inbox?

Action permissions (whether the agent can send directly, read attachments, or organize threads) are set on the agent and apply across every inbox attached to it. When you want different action permissions per account, create two separate agents.

How many inboxes can I attach to one agent?

You can attach every connected mailbox in your comail account to the same agent. The only cap is per mailbox: each inbox supports up to 10 active or paused agents.

What happens if I pause or disconnect one inbox?

The agent loses access to that inbox right away, while its other inboxes and your MCP client connection keep working without any reconfiguration.

Request access

We’re onboarding beta users in small batches. Tell us what you want your agent to handle; specific use cases go to the front of the line.

Clients / harnesses (optional)

Select all that apply.

We’ll only email you about the beta. No card, no newsletter.