Add email tools to Cursor's agent mode through MCP. Send messages, check inboxes, and manage contacts without leaving your editor.
Cursor is an AI-native code editor built by Anysphere that puts AI at the center of your development workflow. With its agent mode and deep codebase understanding, Cursor can tackle complex multi-file tasks. Adding MultiMail via MCP extends that capability to email, letting Cursor's agent send notifications, respond to inquiries, and manage email workflows.
Cursor supports both stdio and SSE transport for MCP servers. The MultiMail MCP server uses stdio, which Cursor handles natively. Configuration goes in ~/.cursor/mcp.json, and once set up, MultiMail tools appear automatically in Cursor's agent mode.
Whether you need to email stakeholders after a code review, send automated deployment updates, or manage a support inbox alongside your codebase, the Cursor and MultiMail integration keeps everything in one place.
Sign up at multimail.dev and create an API key from your dashboard. This key authenticates all MCP server requests.
In the MultiMail dashboard, create a mailbox for Cursor's agent to use. Set oversight mode to gated_send to start, so all outbound emails require your approval.
Create or edit the file at ~/.cursor/mcp.json and add the MultiMail MCP server configuration.
{
"mcpServers": {
"multimail": {
"command": "npx",
"args": ["-y", "@multimail/mcp-server"],
"env": {
"MULTIMAIL_API_KEY": "mm_live_your_key_here"
}
}
}
}In Cursor, switch to agent mode (not ask or edit mode) to use MCP tools. Agent mode allows Cursor to invoke external tools like MultiMail automatically as part of its workflow.
Open the Cursor command palette and check MCP server status, or simply ask the agent to list your mailboxes. If configured correctly, you'll see your MultiMail mailboxes returned.
| Tool | Description | Example |
|---|---|---|
| send_email | Send an email from your agent mailbox to any recipient. | Email a client the updated API documentation after refactoring endpoints. |
| reply_email | Reply to a received email, maintaining the thread context. | Reply to a pull request discussion email with implementation notes. |
| check_inbox | Check a mailbox for new or unread messages. | Check for new feedback emails while working on a feature. |
| read_email | Read the full content of a specific email including headers and body. | Read a bug report email to understand the issue before fixing it. |
| create_mailbox | Create a new agent mailbox on your MultiMail account. | Create a mailbox for a new project's automated notifications. |
| list_mailboxes | List all mailboxes on your MultiMail account. | View available mailboxes before choosing which to send from. |
| get_thread | Retrieve an entire email thread to see the full conversation history. | Review the full email thread with a client before drafting a response. |
| search_contacts | Search your contact list by name, email, or tags. | Find the product manager's email to send a feature update. |
| add_contact | Add a new contact to your MultiMail contact list. | Save a new contractor's email after their first pull request. |
| tag_email | Tag or categorize an email for organization and filtering. | Tag emails related to a specific feature with the issue number. |
| list_pending | List all emails currently awaiting human approval. | Review outbound emails queued by the agent before approving. |
| decide_email | Approve or reject a pending email in the oversight queue. | Approve a status update email after reviewing its content. |
{
"mcpServers": {
"multimail": {
"command": "npx",
"args": ["-y", "@multimail/mcp-server"],
"env": {
"MULTIMAIL_API_KEY": "mm_live_your_key_here"
}
}
}
}Add this to ~/.cursor/mcp.json to connect MultiMail to Cursor's agent mode.
Review the changes in src/api/ since the last commit. Summarize what changed and why, then send an email to [email protected] with the subject 'API Changes Summary' and the review as the body.Ask Cursor's agent to review code changes and email a summary to the team.
Check my MultiMail inbox for any emails tagged 'bug-report'. Read the most recent one, analyze the issue against our codebase, implement a fix, then reply to the reporter explaining what was wrong and how it was fixed.Read a bug report email, fix the issue in code, then reply with the resolution.
{
"mcpServers": {
"multimail": {
"command": "npx",
"args": ["-y", "@multimail/mcp-server"],
"env": {
"MULTIMAIL_API_KEY": "mm_live_your_key_here"
}
},
"database": {
"command": "npx",
"args": ["-y", "@other/db-server"]
}
}
}Use MultiMail alongside other MCP servers in Cursor.
MCP tools are only available in Cursor's agent mode. If you're in ask or edit mode, Cursor won't invoke MultiMail tools. Switch to agent mode by selecting it from the mode dropdown in the chat panel.
Cursor understands your entire codebase. Ask it to generate changelogs, API documentation, or test summaries from your code and include them in emails. This combination of code awareness and email tools is uniquely powerful.
Use the tag_email tool to organize emails by the project or feature you're working on in Cursor. This makes it easy to filter and find relevant correspondence later without leaving your editor.
If you've been working in gated mode all day, ask Cursor to list all pending emails at the end of your session. Review and approve or reject them in batch so nothing sits in the queue overnight.
Email infrastructure built for AI agents. Verifiable identity, graduated oversight, and a 38-tool MCP server. Formally verified in Lean 4.