Skip to main content
Autosend MCP
The AutoSend MCP (Model Context Protocol) server lets you manage email campaigns, automations, templates, contacts, senders, and analytics directly from AI assistants like Claude, Cursor, Codex, Antigravity, and other MCP-compatible clients. It’s a remote MCP server with OAuth that gives AI tools secure access to your AutoSend project, available at:
Instead of switching between your AI assistant and the AutoSend dashboard, you can use natural language to:
  • Create, schedule, and send email campaigns
  • Design and update email templates
  • Build and activate multi-step email automations
  • Browse your contact lists, segments, custom fields, and event definitions
  • Look up verified senders and suppression groups
  • Pull campaign and email activity analytics
  • Switch between AutoSend projects on the fly

Prerequisites

AutoSend Account

Sign up for an AutoSend account to get started.

Verified Domain

Add and verify a domain in AutoSend to send emails from.

Verified Sender

Set up at least one verified sender for sending emails.

Connecting to AutoSend MCP

AutoSend MCP uses a streamable HTTP transport with OAuth 2.0 authentication. When you add the server to your MCP client, the client handles the OAuth authorization flow automatically. You just need to log in to your AutoSend account when prompted. Choose your AI client to get started:

Claude

Claude Desktop and Claude Code

Cursor

Settings UI or config file setup

Copilot

VS Code with GitHub Copilot

Windsurf

Windsurf MCP configuration

Codex CLI

OpenAI Codex command line

Antigravity

Google Antigravity setup

ChatGPT

ChatGPT connector setup

Raycast

Raycast MCP extension

Authentication

AutoSend MCP uses OAuth 2.0 to securely connect to your account. You don’t need to manage any API keys or tokens yourself. Your MCP client handles everything automatically. When you first connect, you’ll be redirected to AutoSend to log in and authorize the connection. Once authorized, your client stores the credentials and refreshes them as needed. Each connection is scoped to a single AutoSend project, so your data stays isolated and secure.

Available Tools

AutoSend MCP exposes 34 tools across 10 categories. Your AI assistant automatically uses the right tools based on your requests.

Projects

Lists & Segments

Contact Properties

Templates

Senders

Suppression Groups

Campaigns

Events

Automations

Analytics

Building Automations

Email automations are multi-step workflows that send sequences of emails triggered by contact actions. You build them through MCP in two stages:
  1. Create a draft with create_automation. You define the entry criteria (contact created, property matches, property changes, or event received), optional exit criteria, and a flat list of steps made up of wait, email, and branch blocks. Drafts never enrol contacts or send anything.
  2. Activate the draft with activate_automation. The tool has a confirmation gate, call it first with confirmed: false to preview the workflow, then again with confirmed: true to start enrolling contacts and sending emails.
A few preconditions to keep in mind:
  • Every email step must reference an automation-type template. Call create_template with templateType: "automation" first, then pass the returned templateId into the step.
  • Before referencing a contact field in a filter, call list_contact_properties so you use the exact bare property name.
  • For event-triggered automations or event-property branches, call list_event_definitions (or get_event_definition for a single event) to discover the available property keys.
Learn more about Email Automations, Events, and Contact Properties.

Guided Workflows

AutoSend MCP includes three guided workflow prompts that walk your AI assistant through multi-step processes. These prompts provide structured instructions so the assistant gathers the right information and calls the right tools in sequence.

create-campaign

A step-by-step workflow to create a draft email campaign:
  1. Gathers data - Fetches your lists, segments, senders, and suppression groups
  2. Asks for details - Campaign purpose, target audience, sender, unsubscribe group, subject line, and preview text
  3. Designs the email - Proposes a template structure and generates responsive HTML
  4. Creates the draft - Calls create_campaign to create the template and campaign together
  5. Reviews - Shows a summary with the campaign ID and next steps

create-template

A step-by-step workflow to create a reusable email template:
  1. Understands purpose - Asks about template type (marketing or transactional), audience, brand style, and sections
  2. Designs HTML - Generates responsive email HTML following email client compatibility best practices
  3. Creates the template - Calls create_template with all metadata
  4. Reviews - Shows a summary with the template ID and next steps

create-automation

A step-by-step workflow to build a draft email automation:
  1. Gathers data - Fetches your lists, segments, senders, suppression groups, custom fields, and event definitions
  2. Asks for details - Automation name, trigger type, exit conditions, number of emails, timing between them, and any branch logic
  3. Designs the workflow - Creates the automation-type templates each step needs and proposes the wait, email, and branch sequence
  4. Creates the draft - Calls create_automation to assemble the workflow as a draft
  5. Reviews - Shows a summary with the automation ID and how to go live with activate_automation
All three prompts support an auto mode. Say “auto”, “take over”, or “just do it” at any point, and the assistant will make reasonable decisions for all remaining steps without asking for confirmation.

Example Conversations

Here are some things you can ask your AI assistant once AutoSend MCP is connected: Campaign management:
  • “Create a newsletter campaign for our March product updates”
  • “Show me all draft campaigns”
  • “Duplicate the Black Friday campaign and update it for our spring sale”
  • “Delete the test campaign I created yesterday”
Template management:
  • “Create a transactional template for order confirmation emails”
  • “Search for templates related to onboarding”
  • “Update the welcome email template with a new header design”
Automation workflows:
  • “Build a 3-email onboarding automation for new Pro plan signups”
  • “Show me all my active automations”
  • “Activate the welcome series draft we built yesterday”
  • “Create an automation that fires when the order_placed event is logged”
Analytics:
  • “What were the open and click rates on last week’s newsletter?”
  • “Show me email activity for the past 30 days”
Projects:
  • “Which AutoSend project am I currently on?”
  • “Switch me to the staging project”
Looking up data:
  • “List all my contact segments and their sizes”
  • “Show me my verified senders”
  • “What suppression groups and custom fields do I have?”
End-to-end workflows:
  • “I want to send a product launch announcement to our Premium Users segment. Walk me through it.”
  • “Help me create a reusable welcome email template with the recipient’s first name and company”

Important Notes

All campaigns created through MCP are saved as drafts. You must publish or send them from the AutoSend dashboard. This is a safety measure to prevent accidental sends.
  • Confirmation gates - send_campaign, send_test_email, and activate_automation all require confirmed: true to actually execute. Call them first with confirmed: false to preview what will happen before committing.
  • Project scope - Each MCP session has one active project at a time. Use list_projects to see all projects you can access and switch_project to change focus mid-session.
  • Template variables - Use Handlebars syntax ({{variableName}}) for dynamic content. Variable names must start with a letter and can include letters, numbers, and underscores.
  • Character limits - Campaign name: 200 characters, subject line: 988 characters, preview text: 140 characters.
  • Email HTML - The MCP server’s guided workflows generate email-safe HTML using table-based layouts, inline CSS, and responsive design patterns that work across all major email clients.
  • Scoped access - Each MCP connection is scoped to a single AutoSend organization. The server cannot access data from organizations you don’t belong to.

Next Steps

AutoSend Skills

Install skill files for additional AI agent context.

API Reference

Full API documentation with all endpoints and parameters.

Campaigns

Learn more about creating and managing email campaigns.

Email Templates

Create reusable email templates with dynamic variables.