For developers: common questions

Is there an MCP server for email?

Yes. Inbox Triage is a remote MCP server at https://getinboxtriage.com/mcp that connects Gmail, Google Workspace, Outlook, Microsoft 365, iCloud, Yahoo, AOL, and other IMAP inboxes, up to 10 on one account, to any MCP app. It uses Streamable HTTP and OAuth 2.1.

Can one MCP connection reach several email accounts?

Yes. Every inbox you connect, up to 10 and from any mix of providers, is reached through the one MCP URL. Tools take an inboxId to pick the inbox.

Which MCP transport does it use?

Streamable HTTP over HTTPS. There is no need to run anything locally.

Do I need an API key?

For MCP, no: if your app supports OAuth 2.1 sign-in it connects without a key. For the REST API, yes: it accepts only a bearer API key. Create one in Settings, under Advanced, after you confirm your email address.

Is there a REST API?

Yes, under https://getinboxtriage.com/api, with a bearer API key. It covers adding, renaming, and removing inboxes, reading, syncing, drafts, the triage profile, and leases. The API reference lists every route with curl, JavaScript, and Python examples.

Can the REST API send email or archive?

No. Archiving, trash, labels, spam reports, unsubscribes, undo, and sending are MCP only, and spam reports, unsubscribes, and sends need the person's approval.

What are the rate limits?

About 120 requests a minute to the REST API and 300 a minute to MCP, per key or connected app. Past that you get HTTP 429 with a Retry-After header in seconds.

Can an agent pass a mail password through a tool?

No. No tool accepts a password, app password, or OAuth code. Connect tools return a link that the person opens.