01
The client asks
It requests some combination of read, draft and send. The request is bound to the browser that opened it and expires after 10 minutes.
Integrations
An MCP email server for the agent you already run
One URL, an OAuth consent screen you control, and six tools scoped to the inboxes you pick.
Email for Agents supplies the inbox and the email tools. Your agent keeps running wherever it runs today — we do not host it, and there is nothing to install on our side. If your client supports remote MCP and OAuth, this is one paste and one consent screen.
https://mcp.emailforagents.ai/mcp What connecting actually does
Nothing is granted by pasting a URL. The client starts an authorization, and you make three decisions in the browser before any tool exists.
02
You choose
The consent screen names the client, the scopes it asked for, and the highest permission it could receive. You pick the project, the specific inboxes, and the permission level — never more than you hold yourself.
03
The grant exists
It covers those inboxes and nothing else, expires after 30 days, and can be revoked sooner from Connections. Replaying a refresh token revokes the whole grant.
The six tools
A tool the grant does not cover is not merely refused — it is not listed, so the agent never sees a capability it cannot use.
list_inboxes Read List the inboxes this grant covers.
list_threads Read List conversations in one of them.
list_messages Read List message ids, recipients, attachment metadata and previews, with a cursor.
get_message Read Read one message body, bounded in size.
create_draft Draft Compose a new message or a threaded reply for a human to release. It cannot transmit mail.
send_message Send Transmit a message, still subject to the inbox's approval policy.
Drafting and sending are genuinely different privileges: the draft path runs with the send scope stripped from the credential, so an agent with draft access cannot reach the send tool by a side door. Tool results are capped at 131,072 characters; past that the server tells the agent to use the scoped REST API for the full body rather than truncating silently.
An API key will not work here, on purpose
The MCP endpoint accepts connection grant tokens and nothing else.
A project API key, a human sign-in session and a test session are all rejected at
/mcp with an explicit error. This is a deliberate boundary, not a gap: an MCP
tool call is made by software acting for a person, and the authority for it has to be
traceable to a human who approved a specific set of inboxes. A shared API key cannot carry
that. The endpoint also answers 405 to a GET, because every MCP exchange is a
POST, and it negotiates protocol versions 2025-11-25, 2025-06-18 and 2025-03-26.
If your client cannot do OAuth, that is what the REST API is for. It is the same permissions and the same send pipeline.
Client status, honestly
No named client is certified, supported or one-click. Every OAuth connection is recorded with a trust class of unverified, whatever opened it — so this table is what we have tried, not a compatibility promise.
Claude Desktop
Testing generic MCP connection — not certified yet
Remote MCP connectors depend on the application and plan.
Claude Code
Testing generic MCP connection — not certified yet
Remote MCP connectors depend on the application and plan.
Cursor
Testing generic MCP connection — not certified yet
Remote MCP connectors depend on the application and plan.
Any other MCP client
Not yet tested
If it speaks remote MCP over HTTP and can complete an OAuth authorization, it should work. We have not verified it.
Anything without remote MCP
Tested API recipe
Use a project-scoped REST key instead. Every MCP tool has a REST equivalent.
Connector availability can also depend on the application and the plan you are on with that vendor, which is outside our control. If a client you use works, we would rather hear about it than guess — who to tell.
Guides about connecting
How to Give an AI Agent Its Own Email Address
Create a dedicated inbox, choose read, draft or send permission, connect over MCP or a scoped key, and prove a real round trip before granting send access.
MCP Email Server: Give Your Agent Client a Real Inbox
How a remote MCP email server works, what the consent screen must show, how to scope a grant to one inbox, and how to verify it before allowing sends.
MCP or API Key for Agent Email? How to Choose
Remote MCP over OAuth or a project-scoped REST key: what each can and cannot do, who authorises it, how revocation differs, and why teams use both.
Connect a test inbox first — it cannot reach a real person.
Create an inbox Follow the connection guide