Connect MultiMail to Cursor for AI-Powered Email

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.

Get started

1

Get your MultiMail API key

Sign up at multimail.dev and create an API key from your dashboard. This key authenticates all MCP server requests.

2

Create an agent mailbox

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.

3

Configure the MCP server in Cursor

Create or edit the file at ~/.cursor/mcp.json and add the MultiMail MCP server configuration.

4

Enable agent mode

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.

5

Verify the connection

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.


Available MCP tools

ToolDescriptionExample
send_emailSend an email from your agent mailbox to any recipient.Email a client the updated API documentation after refactoring endpoints.
reply_emailReply to a received email, maintaining the thread context.Reply to a pull request discussion email with implementation notes.
check_inboxCheck a mailbox for new or unread messages.Check for new feedback emails while working on a feature.
read_emailRead the full content of a specific email including headers and body.Read a bug report email to understand the issue before fixing it.
create_mailboxCreate a new agent mailbox on your MultiMail account.Create a mailbox for a new project's automated notifications.
list_mailboxesList all mailboxes on your MultiMail account.View available mailboxes before choosing which to send from.
get_threadRetrieve an entire email thread to see the full conversation history.Review the full email thread with a client before drafting a response.
manage_contactsSearch your contact list by name, email, or tags.Find the product manager's email to send a feature update.
manage_contactsAdd a new contact to your MultiMail contact list.Save a new contractor's email after their first pull request.
tag_emailTag or categorize an email for organization and filtering.Tag emails related to a specific feature with the issue number.
list_pendingList all emails currently awaiting human approval.Review outbound emails queued by the agent before approving.
decide_emailApprove or reject a pending email in the oversight queue.Approve a status update email after reviewing its content.

Try it with your agent

No code, no dashboard. Paste this to your AI agent — it connects MultiMail, creates an inbox, and builds the flow for you.

You are my Cursor agent. Connect MultiMail for agent email and run in gated_send oversight mode so I approve every outbound email before it sends. 1. Read https://multimail.dev/llms.txt and follow the current MultiMail instructions there. Do not assume any API path, header, webhook, or hidden endpoint. 2. Add MultiMail's MCP server to Cursor so email tools are available in agent mode. Confirm the tools are visible before continuing. 3. Create a free MultiMail inbox for this project, then set up a verified sending domain or verified sender as instructed by MultiMail. 4. Compose a short test email from the verified sender to the new inbox. Before sending, show me the exact recipient, subject, and body for approval. After I approve, send it, check the inbox, summarize the received message, and draft a brief reply without sending it. 5. Keep MultiMail in gated_send mode for this workspace. For any future email, draft first, show me the final content and recipients, and wait for my approval before sending or scheduling.

Best practices

Use agent mode, not ask or edit mode

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.

Leverage codebase context in emails

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.

Tag emails by project or feature

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.

Review pending emails before end of day

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.


Common questions

Does Cursor support stdio and SSE for MCP servers?
Yes, Cursor supports both stdio and SSE transport for MCP servers. The MultiMail MCP server uses stdio transport, which works out of the box with Cursor's MCP implementation. No additional transport configuration is needed.
Why don't MultiMail tools appear in ask or edit mode?
Cursor restricts MCP tool usage to agent mode. In ask mode, Cursor only answers questions. In edit mode, it only modifies code. Switch to agent mode from the mode selector in the chat panel to access MultiMail tools.
Can I use MultiMail with Cursor's multi-file editing?
Yes, MultiMail tools work alongside Cursor's multi-file editing capabilities. You can ask Cursor to refactor code across multiple files and then email the team about the changes, all in a single agent mode session. The email tools don't interfere with code editing tools.
How do I share the MCP config with my team?
The Cursor MCP config at ~/.cursor/mcp.json is user-specific. For team sharing, document the config structure and have each team member add their own API key. Never commit API keys to version control. You can share a template config with a placeholder key.
Can Cursor read emails and use them as coding context?
Absolutely. Ask Cursor to read an email (such as a bug report or feature request) and then use that information to make code changes. Cursor's agent mode can chain together reading an email, analyzing the request against your codebase, implementing changes, and replying to the sender.
What happens if the MCP server disconnects?
If the MultiMail MCP server disconnects during a session, Cursor will show an error when trying to use email tools. Restart the MCP server connection from Cursor's command palette or reload the window. Your pending emails and mailbox state are preserved server-side.

More MCP clients

The only agent email with a verifiable sender

Email infrastructure built for AI agents. Verifiable identity, graduated oversight, and a hosted MCP server. Formally verified in Lean 4.