AgentMail

AgentMail gives AI agents their own email inboxes. Through this connector, an agent (or you, in ChatGPT) can spin up a dedicated inbox on the fly, then send, receive, reply to, and forward email, with full thread context, drafts, and attachments, entirely through tool calls. Unlike traditional email APIs built for one-way notifications, AgentMail is built for two-way conversations: an agent can read an incoming thread, understand it, and respond in context, just like a person would. This makes email a first-class communication and identity channel for agents, letting them sign up for services, coordinate with people, and talk to other agents. Key capabilities exposed over MCP: • Inboxes: create, list, get, update, and delete agent inboxes • Messages: send, reply, forward, list, and update • Threads: list, read, label, and delete full conversation threads • Search: full-text search across threads and messages • Drafts: create, list, read, update, send (with scheduling), and delete • Attachments: retrieve attachments by ID, with text extraction for PDF/DOCX Connect in seconds via OAuth using your AgentMail console identity. No API key required in ChatGPT. Sign up free at console.agentmail.to.

Use the remote MCP URL on this page in your MCP client (Claude, Cursor, VS Code, and more). Copy the endpoint if your client needs a manual entry, then complete provider sign-in when your client connects — tools appear after authentication.

This endpoint requires provider sign-in, so MCPBundles could not list tools anonymously during the last probe. After you connect and authenticate in your MCP client, your session should receive the live tool list from the provider.

AgentMail may require signing in to the provider before tools can run. Connect through MCPBundles or your MCP client and complete any provider login when prompted.