Email for your Cursor agent

AgentMail is the fastest way to give a Cursor agent its own email inbox. Give it a dedicated inbox it can create, read, and reply from.

AgentMail is an official Cursor plugin

View the listing ↗

Start for free Docs

[ Install ]

One command

AgentMail is in the Cursor plugin marketplace. Install it with one command and your Cursor agent can create inboxes, send email, and handle replies like any other tool.

Configure (credentials, email channel, verification)

[ Why email ]

Why your Cursor agent needs its own inbox

One command, no API key

Install from the marketplace with /add-plugin agentmail, then complete the AgentMail OAuth sign-in in your browser the first time the MCP server connects. Nothing to paste into a config file.

Skills, not just tools

The listing bundles 8 skills and the AgentMail MCP integration, so the agent gets guidance on sending, triaging, and managing inboxes alongside the raw tools. Source at github.com/agentmail-to/agentmail-plugins.

No deliverability headaches

AgentMail handles SPF, DKIM, and DMARC. Your agent emails land in inboxes, not spam.

[ Code ]

Working code

[ FAQ ]

FAQ

Common questions about AgentMail and Cursor.

Yes. AgentMail is listed in the Cursor plugin marketplace under Productivity at cursor.com/marketplace/agentmail, created by AgentMail. Install it with /add-plugin agentmail. The listing bundles 8 skills and 1 MCP integration, so one install gives your agent the AgentMail MCP server plus skills for sending mail, checking mail, managing inboxes, the SDKs, the CLI, the toolkit, and agent email patterns. Source is at github.com/agentmail-to/agentmail-plugins.

No. The plugin points at the hosted MCP server and you complete an AgentMail OAuth sign-in in the browser the first time it connects, so there is no key to paste. You only need an AGENTMAIL_API_KEY if you use the SDK or CLI directly, or if you configure MCP by hand instead of installing the plugin.

Yes. Add the hosted endpoint https://mcp.agentmail.to/mcp to ~/.cursor/mcp.json with an x-api-key header, using a key from console.agentmail.to. The manual path uses the API key rather than OAuth. Everything else behaves the same.

Inbox creation and deletion, sending messages, listing and reading messages, replying to threads, managing attachments, and setting up webhooks.

Yes. MCP gives your agent conversational access to email. The SDK gives you programmatic control in code. They use the same API and the same inboxes.

Free: 3. Developer ($20/mo): 10. Startup ($200/mo): 150. Enterprise capacity is tailored to the agreement.

Yes. Every AgentMail inbox is a real email address. Incoming messages are available instantly via the API, MCP, or webhooks.

Gmail API requires OAuth and was built for human accounts, not programmatic agent use. SendGrid handles sending only - no receiving, no threading, no reply parsing. AgentMail gives your Cursor agent a dedicated inbox it can create on demand, send from, receive on, and read - with full thread context and no credential sharing.