How to Send an Email with Claude (No Code Needed)

A founder I know built a SaaS product that now makes almost $1k a month. He has never written a line of code. He built the whole product by chatting with Claude, and he sends every email campaign the same way.

He does not open the AutoSend dashboard to write emails. He opens a Claude chat, describes what he wants to say, asks Claude to send it, and confirms. The dashboard exists on his computer mostly for billing.

That is what this article walks through. If you have an AutoSend account and Claud subscription, you can send a real email campaign in about five minutes without touching the dashboard or writing any HTML.

---

What makes this possible: Email MCP

Claude cannot send emails on its own. What it can do is connect to external tools through a protocol called MCP (Model Context Protocol). When you add the AutoSend Email MCP server to Claude, it gets access to 34 tools: creating templates, building campaigns, targeting contact lists, pulling analytics, managing senders, and sending.

You talk to Claude in plain language. Claude decides which tools to call and in what order. You confirm before anything goes out.

The AutoSend Email MCP server is remote and uses OAuth. That means there is no config file to edit and no API key to paste anywhere. You add a URL, you log in to AutoSend when prompted, and it works.

---

Setup: connecting AutoSend to Claude

You need Claude subscription and an AutoSend account with at least one verified domain and verified sender.

Step 1. Open Claude. Go to Settings, then the Developer tab, and click "Edit Config."

Step 2. Add this to your config file:

{
	"mcpServers": {
		"autosend": {
			"type": "http",
			"url": "https://mcp.autosend.com/"
		}
	}
}

Step 3. Save the file.

Step 4. Claude will prompt you to log in to AutoSend. That is the entire auth flow. OAuth handles the credentials. You do not manage any tokens.

Once connected, you will see the AutoSend tools available in Claude. There are 34 of them across campaigns, templates, contacts, senders, automations, and analytics.

More details on setting up AutoSend Email MCP with Claude

---

Sending your first campaign

Here is what the conversation looks like in practice. You do not need to think about which tools Claude uses. Just describe what you want.

You: I want to send a campaign to my "active users" list announcing our new feature. It's a calendar integration. Keep it short and conversational, no heavy design needed.

Claude will:

1. Look up your contact lists to confirm the right one
2. Look up your verified senders
3. Draft the HTML for the email
4. Create a campaign draft
5. Show you a preview of what will be sent, including subject line, recipient count, and sender

Then it will ask for confirmation before sending. You type yes, and it goes.

The full flow from "I want to send a campaign" to "confirmed and sent" takes about 90 seconds, assuming you already have a list and sender set up.

What actually happens behind the scenes: Claude calls get_lists_and_segments to find your list, list_senders to pick the right sender, create_campaign to build the draft with HTML content, and finally send_campaign with confirmed: false first (so you see a preview) and then confirmed: true when you approve.

---

What you can do in a Claude chat

Because AutoSend MCP exposes the full account, not just a send button, you can handle a surprising amount without touching the dashboard:

Campaign work

• "Write and send a campaign to my newsletter list about X"
• "Schedule a campaign for next Monday at 9am"
• "Duplicate last month's update email and update it for June"
• "What was the open rate on the campaign I sent last Tuesday?"

Automations

• "Build a 3-step onboarding sequence that triggers when a user signs up"
• "Activate the re-engagement automation I set up last week"
• "What automations are currently running?"

Template management

• "Create a welcome email template for new signups"
• "Update my password reset template to mention the new 15-minute expiry"
• "Find all my templates and list them with their last modified date"

List and contact work

• "How many contacts are in my active users segment?"
• "Create a new list called 'beta testers'"

Analytics

• "How did my last three campaigns perform?"
• "Pull the click rate on the feature announcement email"

The one thing you still need the dashboard for is the initial setup: adding a domain, verifying a sender, and managing billing. After that, most of the day-to-day can stay in Claude.

---

The actual workflow of sending emails

The person I mentioned at the start does not think of himself as doing email marketing. He thinks of himself as talking to Claude about his product and occasionally asking it to tell his users something.

His flow looks like this. Every time he ships something, he opens a Claude chat and says something like: "We just added [X]. My users are indie hackers building small tools. Write them a short email, keep it conversational, send it to the 'all subscribers' list."

He reviews what Claude drafts. Sometimes he asks for a different subject line or a shorter email. When he is happy with it, he says send, confirms, and moves on.

That is it. No template builder. No subject line A/B test setup. No scheduling UI. He does his real work in Claude already. Email became part of that same conversation.

---

Why this works for campaigns but developers still want the API

MCP is the right tool when you want to operate in natural language and you do not need to trigger emails programmatically from your codebase.

If your app needs to send a password reset email the moment a user requests one, that has to come from your backend via the AutoSend API or SDK. Your server cannot have a Claude conversation mid-request.

If a non-technical person on your team wants to send a monthly newsletter, check campaign stats, or draft a re-engagement sequence without touching code or learning a dashboard, Email MCP is faster.

Both can coexist. At Peerlist, our transactional emails like verification and password reset run through the API. Our team now uses MCP for campaign work.

---

Getting Claude on other tools

Claude is the simplest entry point, but AutoSend MCP works with several other AI clients: Cursor, Windsurf, GitHub Copilot in VS Code, ChatGPT, Codex, Raycast, and Antigravity. The setup on each is slightly different. The full instructions for each client are in our MCP docs.

If you are building an agent in code and want it to send emails, that is a different path. Our guide on sending emails from AI agents covers the REST API, MCP, and skill approaches with working examples, and what an email API for AI agents actually needs goes deeper on what makes a stack safe for an agent to run on its own.

---

FAQ