Connect Cursor
How to connect Cursor to email (send and reply via MCP)
Connect Cursor to email by adding SendRaven to ~/.cursor/mcp.json, or .cursor/mcp.json in a project, with the URL https://mcp.sendraven.ai/mcp.
Cursor's agent can then send from your own domain, read the replies as threads and answer them, and it asks before each tool call unless you allow that tool.
{
"mcpServers": {
"sendraven": {
"url": "https://mcp.sendraven.ai/mcp"
}
}
}> Write the HTML for our welcome email to match the app's styles, then send a test of it to me at dev@yourcompany.com.Before you start
What Cursor needs.
Cursor, with its agent available on your plan.
A SendRaven workspace with a verified sending domain and a payment method on it. Free includes 3,000 emails a month and is never charged without an upgrade.
An API key in an environment variable if the agent should run under a key's limits; otherwise Cursor signs in through the browser.
Setup
Connect Cursor step by step.
Add the server to mcp.json
Use ~/.cursor/mcp.json to have it in every project, or .cursor/mcp.json to keep it with one. Cursor signs in through the browser the first time a tool is used.
~/.cursor/mcp.json{ "mcpServers": { "sendraven": { "url": "https://mcp.sendraven.ai/mcp" } } }Or connect with a key
Cursor fills ${env:NAME} from the environment, so the key stays out of a file you might commit. Set SENDRAVEN_API_KEY before starting Cursor.
~/.cursor/mcp.json, with a key{ "mcpServers": { "sendraven": { "url": "https://mcp.sendraven.ai/mcp", "headers": { "Authorization": "Bearer ${env:SENDRAVEN_API_KEY}" } } } }Check it in Cursor's MCP settings
SendRaven appears in Cursor's MCP settings with its tools listed and a switch to turn it off. If it shows an error, the MCP Logs in the Output panel say why.
Try it
Three things to ask Cursor.
“Write the HTML for our welcome email to match the app's styles, then send a test of it to me at dev@yourcompany.com.”
Builds the template from the code it can see and sends a test with send_email, so you review it in a real inbox rather than a preview.
“Why did the email to ana@customer.com yesterday not arrive?”
Looks the message up with list_emails and get_email, whose events say whether it was delivered, bounced, suppressed or held.
“Our tests send real email. Point them at SendRaven's simulator address and confirm one send goes through.”
Edits the test configuration and sends one message to success@simulator.amazonses.com, which accepts mail without anyone receiving it.
Once connected
What Cursor can do with email.
Send
From your own verified domain, as plain text, HTML or a stored template, now or at a set time.
- send_email
- send_template_email
- list_scheduled_emails
Read the replies
Replies join the thread they answer on Message-ID, with the quoted history removed, and one call lists what is waiting on you.
- list_threads
- get_thread
- mark_thread_handled
Reply in the thread
The answer goes into the same conversation with the right headers, so it lands under the original in the recipient's inbox.
- reply_to_message
Run sequences and campaigns
Automations that stop when someone replies or unsubscribes, and campaigns that can be previewed before they go.
- create_automation
- enroll_in_automation
- preview_broadcast
Every tool the server has, grouped by what an agent is trying to do.
Safety controls
The limits live on the key, not in the prompt.
Cursor reaches exactly what its credential can reach. Give an agent's API key any of these, and the tools respect them because the API underneath enforces them.
A daily send cap
daily_send_limit stops the key once it has sent that many today, counting scheduled and held mail too.
A recipient allowlist
allowed_recipients takes addresses and whole domains. Anything else is refused before it is written.
An approval hold
requires_approval turns every send into a draft that a person releases. The key cannot approve its own drafts.
A browser sign-in carries none of the three, so use a key for anything that runs unattended. A key also cannot raise its own limits: key management has no MCP tool. Every limit a key can carry.
Troubleshooting
If it does not work.
Cursor asks for permission on every tool call.
That is Cursor's default for MCP tools. Allow the tools you trust, such as list_threads and get_thread, and keep asking for the ones that send.
The server shows an error and no tools.
Open the Output panel and choose MCP Logs. The commonest cause is a key variable that was not set when Cursor started, which sends an empty Bearer header.
It works in one project and not another.
A server in .cursor/mcp.json belongs to that project only. Move it to ~/.cursor/mcp.json to have it everywhere.
Why not just Resend?
Resend has an MCP server too. The difference is what happens after the send.
The reply is a thread, not a webhook
SendRaven: Joined on Message-ID to the message it answers. Resend: a received-email event; you fetch the message and set reply headers yourself.
Per-key daily cap and recipient allowlist
SendRaven: daily_send_limit and allowed_recipients on the key, checked on every send. Resend: keys scope to a domain and to send-only; no cap or allowlist.
Human approval hold on a key
SendRaven: requires_approval drafts the message and waits for a person. Resend: not offered.
From resend.com, last checked 16 September 2026. The full comparison, including where Resend is the better choice.
Questions
Can Cursor send emails?
Yes, through an MCP server for an email service. With SendRaven in mcp.json, Cursor's agent sends from your own verified domain, reads replies as threads and answers them.
Where is Cursor's MCP config file?
~/.cursor/mcp.json for servers you want in every project, and .cursor/mcp.json in a project's root for one project. Both use the same mcpServers shape.
How do I keep an API key out of Cursor's mcp.json?
Write the header as Bearer ${env:SENDRAVEN_API_KEY} and set the variable in your environment. Cursor fills it in when it starts the connection, so the file holds no secret.
Can Cursor test my app's emails without mailing real people?
Yes. Send to success@simulator.amazonses.com, which accepts mail without delivering it to anyone, or give the agent's key a recipient allowlist of your own domain.

Give Cursor an inbox it cannot misuse.
Verify a domain, create a key with the limits you want, and connect. Free includes 3,000 emails a month, inbound included, and is never charged without an upgrade.

