Mailsoftly MCP Server — Run Email Campaigns from Chat

Here’s what most email marketing MCP servers do: they let your AI assistant read campaign stats. You ask, it fetches numbers, you nod along. Fine for a quick glance, but you still have to open the dashboard to actually do anything.

The Mailsoftly MCP server is different. It gives your AI agent real write access to your Mailsoftly account — not just analytics, but the ability to create contacts, subscribe them to lists, and dispatch campaigns to live audiences. That makes it one of the few marketing MCP servers that can move a needle, not just report on one.

But here’s the honest part: it won’t replace your Mailsoftly dashboard. There’s no campaign design, no template editing, no segment builder. If you need those, the web portal is still where you go. What this server is — and what makes it worth installing — is a fast-query operations layer for people who already live inside Claude, Cursor, or VS Code and refuse to tab-switch every time they need to check a campaign or add a contact.

How It Works

The Mailsoftly MCP server sits between your AI assistant and the Mailsoftly REST API. You subscribe through Vinkius, enter your Mailsoftly API key once, and eight tools become available to your agent. No Docker containers, no local setup, no SDK installs. Vinkius Edge handles the connection at https://edge.vinkius.com/YOUR_VINKIUS_TOKEN/mcp, routing requests to the right server based on what you’ve subscribed to.

Every tool execution is visible in the Guardian Control Plane — you can see which tools ran, how long they took, and whether they succeeded. If something looks off, you can revoke access from your Vinkius dashboard at any time. The Security Passport on the server page shows exactly what permissions each tool uses, so there’s no guessing about what your agent is allowed to do with your account.

The Five Tools That Actually Matter

The server exposes eight tools total. Five of them are the ones you’ll reach for in real workflows. Let me walk through why each one matters and show you a prompt you can copy right now.

`send_campaign_to_all` — Dispatch campaigns from chat

This is the only tool in this server that makes things happen in the real world. You give it a campaign ID, and Mailsoftly starts delivering that campaign to every assigned segment and list. No confirmation dialog, no second step — just one call.

That power comes with responsibility. If you accidentally send a draft that isn’t ready, there’s no recall button. My rule: always inspect the campaign with get_campaign_details before sending. Here’s how that looks in practice:

“Show me the details of campaign cp789, then send it to all lists.”

Your agent will first call get_campaign_details to verify what’s actually in that campaign — subject line, assigned segments, content preview — and only then trigger send_campaign_to_all. This two-step habit is worth building.

`get_campaign_click_data` — Click engagement without the dashboard

Most email platforms bury click data behind three clicks: open the campaign, find the analytics tab, filter by date, scroll to the table. With this tool, you get unique click counts and individual subscriber click data in one prompt.

“Show click statistics for sent campaign ID cp456.”

The agent returns something like: 145 unique clicks from 120 individual subscribers. That’s enough to decide whether a campaign is performing or whether you need to adjust your subject line for the next send. Pair this with list_sent_history to quickly scan which campaigns went out recently, then drill into the one that matters.

`create_base_contact` and `add_contact_to_list` — The contact workflow

These two tools work as a pair. Mailsoftly requires you to create a contact record first (minimum: an email address), then subscribe that contact to a specific list. There’s no single “add and subscribe” tool — it’s always two steps.

Here’s the workflow in natural language:

“Create a contact for newlead@startup.io, then add them to my newsletter list.”

Your agent will call create_base_contact with the email address, receive confirmation, then call add_contact_to_list with the email and the list ID. The catch? You need to know the list ID ahead of time. If you don’t have it memorized (and honestly, who does?), chain in list_subscriber_collections first:

“Show me all my contact lists, then add newlead@startup.io to the newsletter one.”

This is where AI agents actually earn their keep — chaining three tools together so you never have to look up an ID manually.

`list_marketing_campaigns` — Your campaign inventory at a glance

Before you drill into details or check click data, you often need to know what campaigns even exist in your account. This tool retrieves every email campaign — active drafts, sent ones, everything — and returns names with their IDs. It takes no parameters, so it’s the fastest first step in any workflow.

“List all my email campaigns in Mailsoftly.”

The agent returns something like: Launch Event 2024 (ID: cp123), Monthly Roundup, Welcome Series. Now you have the IDs to pass into get_campaign_details, get_campaign_click_data, or send_campaign_to_all. Without this tool, you’d need to remember campaign IDs from memory or open the dashboard to look them up. With it, discovery is one prompt away.

`get_campaign_details` — Pre-flight inspection

Before you send anything, before you make decisions based on campaign data, check what you’re actually working with. This tool returns metadata and configuration for any campaign by ID — subject line, body content, assigned segments, status. Think of it as the “are we sure?” step before every destructive action.

A common pattern: list all campaigns with list_marketing_campaigns, pick one by name or ID, then call get_campaign_details to verify it’s configured correctly. This is especially useful when you’re managing multiple campaigns and want to confirm which segments a particular campaign targets before triggering a send.

A Real Morning With the Mailsoftly MCP Server

Let me walk through a realistic scenario. You’re a growth engineer at a startup running about a dozen campaigns across four subscriber lists. Normally, your Monday morning routine looks like this: open Mailsoftly in a browser, navigate to campaigns, check which ones sent last week, pull click data for the latest newsletter, see if any new leads from your product need to be added to the welcome list.

With the MCP server connected to Claude Desktop (or Cursor, or VS Code), that same routine becomes a conversation:

“Show me all campaigns I’ve sent in the last week.” — The agent calls list_sent_history and returns the dispatch history with campaign names and IDs.
“What were the click numbers on the product update newsletter?” — You identify the campaign from step one, and the agent calls get_campaign_click_data to pull engagement metrics.
“Two new trial users signed up yesterday — add sarah@techcorp.com and mike@startup.io to my welcome list.” — The agent chains create_base_contact for each email, then add_contact_to_list to subscribe them. If those contacts already exist, the create step simply returns the existing record — no duplicate errors.
“Is the holiday promo campaign ready? Show me the details before I send it.” — The agent calls get_campaign_details with the campaign ID so you can verify content and assigned segments. You review the preview, give the go-ahead, and the agent calls send_campaign_to_all.

That’s four prompts instead of fifteen clicks across three dashboard pages. For someone who does this daily, the time savings compound fast.

What Mailsoftly MCP Server Can’t Do

This section matters because overstating what an MCP server can do destroys trust. The Mailsoftly server is powerful for operations it does cover, but these gaps are real:

You can’t create new campaigns. There’s no tool to draft a campaign, write subject lines, or compose email content. Campaign creation happens in the Mailsoftly web portal. The MCP server only manages campaigns that already exist.

You can’t edit campaign templates or content. If you need to change the body of an existing campaign or swap out a CTA button, open the dashboard. The MCP tools are read-only for campaign content — get_campaign_details shows you what’s there, but nothing modifies it.

You can’t create new subscriber lists. The list_subscriber_collections tool reads list metadata; it doesn’t create lists. If you need a new segment or audience bucket, that’s a portal operation.

You can’t unsubscribe contacts or delete them. There’s no remove-contact tool and no unsubscribe endpoint exposed through MCP. If someone asks to be removed from your list, you’ll need the web interface.

You can’t schedule sends for future dates. The send_campaign_to_all tool triggers immediate delivery. There’s no scheduling parameter — it goes out now, or you don’t send it through this tool.

You can’t see open rates or bounce data. Click-through data is available via get_campaign_click_data, but broader engagement metrics like open rates, bounce rates, and unsubscribe rates aren’t exposed. If those numbers matter to your analysis, the dashboard still holds them.

If any of these gaps are deal-breakers for your workflow, the MCP server isn’t a full replacement — it’s an accelerator for the operations it does cover. Use both. That’s fine.

When to Use It and When Not To

Here’s a decision framework based on what you’re trying to accomplish:

Use the Mailsoftly MCP server when:

You need to check campaign performance quickly without leaving your IDE or chat interface
You’re adding contacts discovered during development, support calls, or demos
You want to dispatch a pre-built campaign from within your AI workflow
You’re chaining marketing operations with other MCP tools (analytics, CRM, project management) in a single conversation

Stick with the Mailsoftly dashboard when:

You’re designing a new campaign or editing existing content
You need to create subscriber lists or build audience segments
You require open rates, bounce data, or detailed delivery reports
You’re managing unsubscribes or deleting contacts
You want to schedule a send for a specific date and time

The sweet spot? Use the MCP server as your fast lane for daily operations — checking stats, adding leads, dispatching ready campaigns. Reserve the dashboard for campaign design and audience management. They complement each other better than either could replace the other.

Connecting the Mailsoftly MCP Server

You can find and subscribe to the Mailsoftly MCP server at https://vinkius.com/apps/mailsoftly-mcp. Subscribe through your Vinkius account, enter your Mailsoftly API key when prompted (grab it from Account Settings → API in your Mailsoftly dashboard), and connect via the Vinkius Edge endpoint.

From there, Claude Desktop, Cursor, VS Code, Windsurf, Claude Code, and any MCP-compatible client can start calling tools immediately. No local installation required — the server runs remotely through Vinkius Edge, which handles authentication, routing, and rate limiting behind the scenes.

The server carries a Silver trust tier with an official publisher status, meaning it’s maintained by the Mailsoftly team themselves. Check the Security Passport on the server page to see exactly what permissions each tool requires before you connect.

The Bottom Line

Most email marketing MCP servers are glorified analytics viewers — they show you numbers but can’t act on them. Mailsoftly flips that: it gives your AI agent real operational power over contacts, lists, and campaign dispatches. That makes it genuinely useful for daily workflows, not just occasional dashboard checks.

The limitations are real too. No campaign creation, no content editing, no scheduling. If you need those, the web portal remains necessary. But for the operations it does cover — checking click data, adding contacts, sending campaigns — this server turns fifteen clicks into three prompts. For anyone living inside an AI assistant, that’s a difference worth making.