Connect VS Code
How to connect VS Code to email (send and reply via MCP)
Connect VS Code to email by adding SendRaven as an MCP server for Copilot: run MCP: Add Server from the Command Palette, choose HTTP and enter https://mcp.sendraven.ai/mcp.
Copilot's agent can then send from your own domain, read replies as threads and answer them, alongside the code it is working on.
https://mcp.sendraven.ai/mcp> Write an integration test that sends through SendRaven to success@simulator.amazonses.com and asserts the send was accepted.Before you start
What VS Code needs.
VS Code with GitHub Copilot, with Copilot chosen as the agent in the chat.
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.
A trusted workspace: VS Code does not start a workspace's MCP servers in Restricted Mode.
Setup
Connect VS Code step by step.
Add the server
Run MCP: Add Server from the Command Palette, choose HTTP, enter the URL and name it sendraven. VS Code offers to sign in when the first tool needs it.
Server URLhttps://mcp.sendraven.ai/mcpOr write it into the workspace
A .mcp.json at the workspace root is shared with everyone who opens the repository. ~/.copilot/mcp-config.json holds the same shape for you alone.
.mcp.json{ "mcpServers": { "sendraven": { "type": "http", "url": "https://mcp.sendraven.ai/mcp" } } }Pick the tools
The server brings 72 tools, and Copilot accepts up to 128 per request across every server. In the chat's tool picker, keep the ones this workspace needs.
Try it
Three things to ask VS Code.
“Write an integration test that sends through SendRaven to success@simulator.amazonses.com and asserts the send was accepted.”
Writes the test against the API and runs one send with send_email to the simulator address, which accepts mail without delivering it to anyone.
“Look up the last five emails sent to beta@yourcompany.com and tell me which were opened.”
Uses list_emails filtered by recipient and get_email for each, whose events include opens and clicks once they are counted.
“Pause the onboarding automation while I fix the typo in step 3.”
Calls set_automation_status. Pausing holds everyone where they are, so nobody loses their place in the sequence while you edit it.
Once connected
What VS Code 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.
VS Code 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.
Copilot says it has too many tools.
Copilot accepts up to 128 tools per request across all servers. Open the tool picker in the chat and turn off the SendRaven tools, or other servers' tools, this workspace does not use.
The server in .mcp.json never starts.
VS Code does not start a workspace's MCP servers in Restricted Mode. Trust the workspace, then start the server again.
An input variable for the key is ignored.
Prompted inputs belong to the older .vscode/mcp.json format, which VS Code is retiring. Use ${NAME} to read the key from the environment instead.
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 VS Code's Copilot send emails?
Yes, through an MCP server for an email service. With SendRaven added, Copilot's agent sends from your own verified domain, reads replies as threads and answers them.
Where does VS Code keep MCP servers now?
In .mcp.json at the workspace root, or ~/.copilot/mcp-config.json for yourself. The older .vscode/mcp.json still works but VS Code has marked it for removal.
Why does VS Code limit MCP tools to 128?
Copilot sends at most 128 tools with a request, counted across every server. Turn off the tools a workspace does not need in the chat's tool picker.
Can I share the SendRaven server with my team in VS Code?
Yes. Commit .mcp.json at the workspace root and everyone who opens the repository gets the server. Leave the key out of it: each person signs in, or reads their own key from the environment.

Give VS Code 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.

