Yogini Bende • 12 Jun, 2026 • how to guide
Last month, Peerlist's monthly campaign went out to 237,000 people. Nobody on our team opened the email dashboard to do it. We designed the email, sent a test, fixed the copy, and hit send, all from a single Claude chat using the AutoSend MCP server.
That is not a demo we staged for a launch video. It is how we run our own email now.
57% of AutoSend users have connected our MCP server. It went from a side feature to the main way people use the product faster than anything we have shipped.
In this guide I will cover what an email MCP server is, every tool ours exposes, how to install it in Claude, Claude Code, and Cursor, and what our customers actually do with it.
MCP (Model Context Protocol) is an open standard that lets AI assistants like Claude connect to outside tools. An MCP server is the thing on the other end of that connection. It tells the assistant what it can do and executes the work.
An email MCP server, then, is an MCP server that gives an AI assistant control over email infrastructure. Connect one, and Claude stops being a writing assistant that drafts copy for you to paste somewhere. It becomes the operator. It can build the template, pick the audience, send the test, and ship the campaign.
The AutoSend MCP server lives at https://mcp.autosend.com/. It is a remote server with OAuth, which means there is nothing to install on your machine and no API key to copy around. You add the URL to your AI tool, log in to AutoSend once, and you are connected.
The server exposes over 30 tools across six areas. Your assistant picks the right ones based on what you ask for, so you never call them by name. Here is the full surface.
Campaigns. Create a campaign, update it, duplicate last month's, schedule or send it, and delete drafts you abandoned. You can say "duplicate the May newsletter, swap the hero section for the new feature announcement, and schedule it for Tuesday 9 AM" and the whole thing happens in one exchange.
Templates. Create and update email templates, search your existing ones, and send yourself a test. This is the part that surprised me most in practice. Claude is good at writing HTML email, and with the template tools it can iterate on design directly in your account instead of handing you code to paste.
Contacts, lists, and segments. Fetch your lists and segments for targeting, create new lists, and read your custom contact fields so personalization variables resolve correctly. When you ask to send a campaign "to everyone who signed up in the last 30 days," the assistant looks up the matching segment itself.
Senders and suppression groups. Look up your verified senders, create new ones, and manage suppression groups so unsubscribe handling stays correct no matter who pressed send.
Automations. This is the newest addition. The MCP server can now create entire automation workflows, list the ones you have, and activate them. One of our customers runs an agency. He started a Claude chat, described his client's product, worked out the right onboarding flow in conversation, then had Claude build that exact automation through the MCP server. He never opened the dashboard. The workflow he discussed is the workflow that went live. If you want the background on designing these flows, I wrote about it in our marketing automation workflow guide.
Delivery stats and analytics. Pull campaign analytics and overall email activity. "How did last week's campaign do compared to the one before it" is now a question you ask in chat, with real numbers in the answer, pulled from the same data you would see in your email metrics.
The server works with Claude, Claude Code, Cursor, Codex, Copilot, Windsurf, Antigravity, ChatGPT, and Raycast. Here are the three setups people ask about most. The docs cover the rest.
AutoSend and enter the URL https://mcp.autosend.com/One note: Claude Desktop does not support remote MCP servers through the claude_desktop_config.json file. Use Connectors.
One command in your terminal:
claude mcp add autosend --transport http https://mcp.autosend.com/
The first time Claude Code uses an AutoSend tool, it opens your browser to authorize the connection.
Add this to your .cursor/mcp.json, either project level or global:
{
"mcpServers": {
"autosend": {
"url": "https://mcp.autosend.com/"
}
}
}
Cursor shows a Needs login prompt once the server is added. Click it and authorize.
You need an AutoSend account, a verified domain, and a verified sender before anything can go out. That part still happens in the dashboard, once.
The MCP server launched as a developer feature. The people using it hardest are not developers.
A CTO at one of our customers, a company we migrated off SendGrid, messaged me a few weeks after the switch. The part of his message that stuck with me: their non-technical teams now use the MCP in Claude to compile and send reports. People who would have filed a ticket for the engineering team are shipping emails themselves. If you are weighing a similar move, our SendGrid comparison covers the migration path.
A pattern across our customer base I did not predict: founders who are vibe coding their products wire up email through the MCP server too. Their agent builds the app, and the same agent sets up the transactional emails. They never read our API reference. Their tools did.
And one of our larger customers sends every campaign through MCP now. Not as an experiment. It is simply faster than the dashboard once you trust it.
Most email tools that offer agent access hand you an API key and a local server to run. That sounds simple if you are a developer. For everyone else, "run npm install and paste your key into a JSON file" is where the journey ends. Many people get overwhelmed at exactly that step, and I do not blame them.
OAuth removes the step. Any marketer, any founder, anyone who can chat with Claude can connect AutoSend and send their first email within ten minutes, from the same chat window. No terminal. No key to find, store, or accidentally commit to a repo. Each connection is scoped to a single AutoSend project, and you can revoke it from your account at any time.
No. Campaigns created through the MCP server are drafts. Sending requires your confirmation. The assistant can prepare everything, and you stay the person who pulls the trigger. We made that decision early, because one bad story about an agent blasting 200,000 people by mistake would undo all the trust this product depends on.
Test sends go to you, so the safe loop is the natural one: build, test in your inbox, then confirm the real send.
I mentioned the Peerlist monthly campaign at the top. Here is the actual loop. We open Claude, ask it to draft this month's edition based on what shipped, and it creates the template in AutoSend. We send a test to ourselves, read it on a phone, ask for changes in plain English, and Claude updates the template through the same connection. When it reads right, we confirm the send to 237,000 subscribers. The dashboard stays closed the whole time.
If you want your email stack to work like that, connect the AutoSend MCP server and send your first campaign from a chat. It takes about ten minutes, and most of that is writing the email.
What is an email MCP server? An email MCP server is a Model Context Protocol server that lets AI assistants like Claude manage email infrastructure: creating templates, sending campaigns, managing contacts, building automations, and checking delivery stats through natural language.
Which AI tools work with the AutoSend MCP server? Claude Desktop, Claude Code, Cursor, OpenAI Codex, GitHub Copilot, Windsurf, Google Antigravity, ChatGPT, and Raycast. Any MCP client that supports remote servers with OAuth can connect.
Can an MCP server send emails directly? Yes, with guardrails. The AutoSend MCP server can send test emails to you immediately. Real campaigns are created as drafts and only go out after you confirm, so an assistant cannot email your list by accident.
Can the AutoSend MCP server create automations? Yes. It can create complete automation workflows, list existing ones, and activate them. You can design an onboarding or re-engagement flow in conversation and have it built in your account in the same chat. See our email automation feature for what these flows can do.
Is the AutoSend MCP server secure? It uses OAuth 2.0, so there are no API keys to manage or leak. Each connection is scoped to one AutoSend project, and you can revoke access from your account whenever you want.
Is there an MCP server for Gmail or Outlook? Yes, community and official servers exist for inbox providers like Gmail and Outlook. Those handle reading and managing a personal inbox. AutoSend's MCP server covers the sending side: campaigns, transactional templates, automations, and deliverability infrastructure for your product.
Do I need to know how to code to use it? No. Adding the server in Claude Desktop is a settings change and a login. More than 70% of our users have connected it, and many of them are marketers and founders, not developers.
Related Articles
Still wondering?
See what your favorite LLM has to say about us,
then make an informed decision.
