Sendflo Now Works as an MCP Server — Run Email Campaigns from Claude, Cursor, and Windsurf

The most common request we got after launching AI email generation was some version of: "Can I just tell it to send?" Not generate a draft, not give me a subject line to copy — actually send. So we built the MCP integration. Sendflo now works as an MCP server, which means you can connect it to Claude Desktop, Cursor, Windsurf, Zed, or any MCP-compatible AI and run your email marketing from there.

This is not a chatbot that writes copy for you to paste somewhere else. When you tell your AI to send a campaign, it sends the campaign. Contacts get created. Segments get queried. Emails go out. You stay in one window.

What MCP actually is

MCP (Model Context Protocol) is an open standard for connecting AI tools to external services. The short version: instead of each AI app building its own Sendflo integration, we publish one server and every MCP-compatible app can use it. Claude Desktop, Cursor, Windsurf, Zed, Cline, GitHub Copilot — they all work with the same config.

The difference from previous AI email tools is execution. Earlier tools could draft copy or suggest subject lines. An MCP tool reads your real contact list, creates a real campaign, and hits send. The AI is not generating suggestions. It is operating your account.

What you can do with it

Four tool calls. One message. No dashboard, no segment ID copied, no send button clicked.

Other things you can ask:

• "What's my open rate this month?"
• "How many credits do I have left?"
• "Add Priya Sharma, phone 9876543210, to contacts tagged VIP"
• "Show me all draft campaigns"
• "Score my contacts and tell me who the hot leads are"
• "List all my segments"

The 11 tools available

Eleven tools, each mapped to a real action in your account:

• list_contacts — list contacts, filter by tag
• create_contact — add a contact with name, phone, email, tags
• list_segments — list all contact segments
• list_campaigns — list campaigns, filter by status
• get_campaign — get campaign stats by ID
• create_email_campaign — create a draft email campaign
• send_campaign — send a campaign to its segment
• get_analytics — credits, plan, total sent, avg open rate
• generate_email — AI-generate subject + HTML from a prompt
• score_contacts — score contacts hot/warm/cold by engagement (Pro)
• list_workspaces — list agency sub-workspaces

How to set it up

You need a Sendflo account, an API key, and an MCP-compatible app. Claude Desktop, Cursor, Windsurf, and Zed all work. The config is identical across all of them.

Step 1: Install uv

uv handles the Python runtime. You don't need to install Python or manage versions.

Step 2: Get your Sendflo API key

Go to app.sendflo.io → Settings → API Keys → Create. Copy the key starting with sk_sf_.

Step 3: Add Sendflo to your AI app config

Open your MCP config and paste this:

Where to find the config file:

• Claude Desktop (Mac): ~/Library/Application Support/Claude/claude_desktop_config.json
• Claude Desktop (Windows): %APPDATA%\Claude\claude_desktop_config.json
• Cursor / Windsurf / Zed: check Settings → MCP in your app

Step 4: Restart and go

Quit your app fully and reopen it. In Claude Desktop, Sendflo tools show under the hammer icon. In Cursor and Windsurf, check the MCP panel in settings.

Auth

No new login, no OAuth. The MCP server uses the same sk_sf_ bearer token that powers the Zapier integration and REST API. Create one under Settings → API Keys, drop it in the config, done.

Agency accounts: each workspace gets its own API key and its own config entry. The list_workspaces tool returns all sub-workspace IDs if you need to look one up.

Where this fits in practice

The dashboard isn't going away. Building templates, configuring sending domains, managing billing — that still happens there. What the MCP integration removes is the constant switching for operational stuff: checking stats mid-conversation, adding a contact someone just mentioned, sending a campaign you already planned.

If you already live in Claude, Cursor, or Windsurf most of the day, you've got one fewer context switch. The more interesting use case is automation — triggering campaigns off external events through an AI agent, rather than manually. A deal closing in your CRM, a signup hitting a threshold, a product launch date arriving. The MCP server handles the Sendflo side; how you wire the trigger is up to you.