Mailingwork MCP for AI. Manage campaigns and segment lists via chat.

Q: How do I check campaign performance using Mailingwork MCP Server?

Call listmailings to get a list of all campaigns. Then, ask for the metrics on a specific ID or name. The agent pulls open rates and click data directly.

Q: Can I update a subscriber's details using Mailingwork MCP Server?

Yes, use updatesubscriber. You provide the unique subscriber ID and specify what fields you need to change (like email or status). It updates the record in place.

Q: What is the best way to segment my audience with Mailingwork MCP Server?

Use listtags first to see all available tags. Then, ask your agent to filter using those tags or use listsubscribers to build a custom list based on multiple criteria.

Q: How do I list all available subscriber groups using the listlists tool with Mailingwork MCP Server?

You call the listlists tool. This command retrieves a full catalog of every mailing list you own. The output provides the unique name, ID, and current total count for each group.

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Connect to your AI in seconds.

Mailingwork executes professional email marketing campaigns using your AI client. It handles advanced audience segmentation, A/B testing, and list management while keeping GDPR compliance top-of-mind.

You manage every aspect of your mailing program—from creating subscribers to analyzing click maps—all through natural conversation with your agent.

What your AI can do

Create subscriber

Adds a new contact to your mailing list.

Get mailing

Retrieves detailed information about a specific campaign or mailing.

Get subscriber

Pulls all data for one specified subscriber ID.

+ 7 more capabilities included

Manage subscriber lists

Create new contacts, retrieve details on specific subscribers, and list all available mailing segments.

Run campaigns and get metrics

List past mailings or campaign summaries, and pull deep analytics like open rates and click map data for performance reviews.

Send targeted emails

Dispatch one-off transactional emails (e.g., password resets) or trigger complex automated workflows based on user actions.

Update audience data

Modify existing subscriber records, updating fields like status or preferences without touching the main list structure.

Check compliance and tags

List all available segmentation tags and confirm GDPR consent settings for any segment you are targeting.

Ask an AI about this

Included with Plan

Waiting for input…

AI Agent

Mailingwork MCP Server: 10 Tools for Email Marketing

These tools let you create subscribers, list campaigns, update data, and send emails—all managed through conversational prompts.

Make your AI actually useful.

Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.

Start using Mailingwork on Vinkius

Create Subscriber

Adds a new contact to your mailing list.

Get Mailing

Retrieves detailed information about a specific campaign or mailing.

Get Subscriber

Pulls all data for one specified subscriber ID.

List Lists

Shows you every segment list available in your account.

List Mailings

Lists all past and scheduled campaigns/mailings.

List Subscribers

Fetches a list of multiple subscribers based on provided filters.

List Tags

Returns all existing segmentation tags you can use to filter lists.

Send Transactional Email

Sends an email for a specific action, like sending a user's order confirmation.

Trigger Automation

Starts a pre-built workflow or automated process within Mailingwork.

Update Subscriber

Changes details for an existing subscriber, like updating their name or status.

Security and governance baked right in.

Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.

Claude AI

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.

Start a conversation

Open a new chat. The Mailingwork integration is available immediately — no restart needed.

Antigravity

Configure Agent Environment

Open your Antigravity agent's workspace configuration or mcp-servers.json file.

Bind the Endpoint

Add the Vinkius endpoint URL to your agent's MCP connections list:

"mcp_servers": {
  "mailingwork": {
    "serverUrl": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
  }
}

Provide your secure token in place of [YOUR_TOKEN_HERE] to ensure your agent requests are authenticated.

Execute

Start your Antigravity session. The agent will autonomously discover and utilize the Mailingwork tools with full Vinkius guardrails applied.

VS Code Copilot

⚡

One-Click Install (Recommended)

In your Vinkius Dashboard, simply click the Add to VS Code button for this server. We'll automatically configure your local workspace.

Or configure manually

Open MCP Settings

Open VS Code, press Ctrl/Cmd + Shift + P, and search for GitHub Copilot: MCP Servers.

Add Server Config

Add the Vinkius endpoint configuration to your mcp-servers.json file:

"mailingwork": {
  "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}

Ensure you replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.

LangChain

Install Dependencies

Install the LangChain MCP adapters for your environment:

pip install langchain-mcp-adapters

Connect the Server

Use the SSEClient in LangChain to connect to the Vinkius managed endpoint:

from langchain_mcp_adapters.client import SSEClient

# Connect to Vinkius
client = SSEClient(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
tools = client.get_tools()

CrewAI

Define the Tool

Load the Vinkius MCP tools into your CrewAI agents:

from crewai import Agent
from mcp_crewai import MCPTool

# Connect securely to Vinkius
vinkius_tools = MCPTool(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")

# Assign to Agent
researcher = Agent(
    role='Data Researcher',
    tools=vinkius_tools.get_all()
)

Execute Task

Run your CrewAI process. The agent will autonomously route tasks to the Vinkius managed server.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

Import from OpenAPI, Swagger, or YAML specs
Create Agent Skills with progressive disclosure
Deploy to edge with MCPFusion framework
Built in DLP, auth, and compliance on every call
Real time usage dashboard and cost metering
Publish to catalog or keep private

Start building

Make Your AI Do More

Start with Mailingwork, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.

Use this MCP plus 5,100+ others, all in one place
Add new capabilities to your AI anytime you want
Every connection is secured and compliant automatically
Track usage and costs across all your servers
Works with Claude, ChatGPT, Cursor, and more
New servers added to the catalog every week

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Mailingwork. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

Your data is protected. See how we built it.

Works with Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This connection provides 10 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.

Segmenting and analyzing lists shouldn't involve jumping between tabs.

Right now, segmenting an audience means exporting a list from the CRM, opening it in Excel, manually adding criteria (like 'opened last week' AND 'clicked product X'), and then figuring out which ID to use for the next platform. It’s three different systems and at least five manual steps.

With this MCP Server, you tell your agent: 'Give me everyone who opened Newsletter A but hasn't clicked on Product B.' The server handles the complex cross-referencing using tools like `list_subscribers` and `list_tags`, giving you a clean, ready-to-use list right in your chat.

Mailingwork MCP Server: Send critical emails with one command.

Sending an order confirmation or a password reset usually requires logging into the platform, finding the specific template, and manually inputting user details. If you miss a step, the email fails or looks wrong.

Now, your agent executes `send_transactional_email`. You just provide the necessary parameters—the recipient ID, the subject line, and the type of confirmation—and the system sends it correctly, every time.

Support 24/7 support@vinkius.com ↗

Security Vinkius Trust Center ↗

SLA Service Level Agreement ↗

Report Listing Send Report ↗

What your AI can actually do with this

You connect your AI client to Mailingwork for professional email marketing campaigns. You manage everything—from building out segments to running deep analytics—all without ever leaving your chat window.

Managing Your Audience Lists
You don't have to build lists manually; you can tell your agent to handle the heavy lifting of subscriber data. Use create_subscriber to add a brand-new contact right away. Need details on one person? Just ask, and it runs get_subscriber to pull all their specific data. If you need to modify someone's info—like changing their status or updating a field—you run update_subscriber.

To see who you’re dealing with, your agent can fetch multiple subscribers using list_subscribers based on filters you give it.

For segmenting people, the system knows all its segments. You can get a full list of every available mailing segment by calling list_lists, and if you need to filter that further, list_tags shows you all the existing segmentation tags you've set up. This whole process keeps compliance front-of-mind; your agent confirms GDPR consent settings for any group you target.

Running Campaigns and Checking Performance
Mailingwork executes campaigns through multiple tools. You can review what’s happened historically by calling list_mailings, which shows a summary of all past or scheduled campaigns. To get deep performance metrics on a specific job, run get_mailing to pull detailed data for that campaign. This doesn't just give you open rates; it gives you full analytics like click maps and delivery stats so you know exactly how well the emails landed.

Sending Targeted Emails and Automating Actions
Sometimes you don’t need a big campaign. You might only need to send one off email, like an order confirmation or a password reset—for that, use send_transactional_email. For complex actions, your agent triggers automated workflows using trigger_automation, starting any pre-built process within Mailingwork when certain events happen.

What You Can Do with This Server:

Segmenting People: You can tell the system to pull lists of subscribers by checking all available tags or listing every segment you've created. You get a full picture of who owns the list.
Tracking Campaigns: You can review summaries of past campaigns via list_mailings and then dive deep into performance reports using get_mailing to check open rates or click maps.
Fixing Data: If someone's details are wrong, you run update_subscriber. Need a new contact? Run create_subscriber.
Action Items: You can send immediate transactional emails with send_transactional_email, and even start automated processes using trigger_automation.

Built · Hosted · Managed by Vinkius Mailingwork MCP Server - Email Marketing Automation

Server ID 019dd11d-e314-72dc-a229-430d72b3e172

Vinkius Inspector

Compliance Grade A+

Score 100/100

Report View Report ↗

Here's how it actually works

The bottom line is: You talk about marketing tasks, and the server performs the necessary actions using specific Mailingwork tools.

Subscribe to the server and provide your Mailingwork credentials.

Your AI client accesses the dedicated tools, allowing you to reference specific list IDs or campaign names in conversation.

The agent executes the tool call (e.g., list_mailings) and returns structured data that your client can interpret directly.

Who is this actually for?

This is for email marketers and agency owners who spend too much time manually clicking through dashboards just to pull a single metric or segment list. It’s for anyone whose job involves running campaigns, managing large lists, or proving ROI—people tired of jumping between the CRM, analytics dashboard, and spreadsheet.

Email Marketer

Uses list_mailings to track performance metrics for seasonal campaigns and uses create_subscriber when a new lead comes in.

Marketing Operations Specialist

Manages data integrity by calling update_subscriber and running trigger_automation workflows based on list changes or external events.

Digital Agency Account Manager

Handles multiple client accounts by using list_lists to confirm which segments are active for different clients, ensuring GDPR compliance before sending any mailings.

What Changes When You Connect

You get real-time performance data. Instead of logging into the analytics dashboard, you ask your agent to 'Show all campaigns and performance for this month,' getting immediate metrics on open rates and clicks from list_mailings results.

Compliance is built in. You can confirm GDPR consent status or list available tags using list_tags, ensuring that any segment you target has the necessary user permissions before running a campaign.

You save time on data retrieval. Need to know if a specific contact exists and what their preferences are? Use get_subscriber instead of hunting through massive export files, getting clean data points instantly.

Automation is immediate. If a user hits a key milestone (like signing up), you don't have to manually send an email; you just call trigger_automation, letting the system handle the rest.

You control every message flow. Beyond newsletters, use send_transactional_email for critical one-off messages—think password resets or order confirmations—ensuring brand consistency across all communications.

See it in action

01 01

The quarterly review.

A manager needs to prove ROI. They ask the agent: 'Show me total recipients and average click rate for Q1.' The agent calls list_mailings and synthesizes the data, providing a single summary report showing 35% average open rates across all campaigns.

02 02

Onboarding new clients.

An account manager has 20 new leads. Instead of manually adding them one by one, they use list_subscribers with a bulk filter and then call create_subscriber for the entire group, making sure all accounts are instantly active.

03 03

Fixing an inactive segment.

A campaign is failing because some users opted out. The user asks to 'find everyone who unsubscribed last week.' The agent uses list_subscribers with a date range and then confirms the status by calling get_subscriber on a few test accounts.

04 04

Handling an order update.

A user just placed an order. Instead of sending it through a separate platform, the agent is prompted to 'Send the final receipt for Order #456.' The tool calls send_transactional_email, completing the communication loop instantly.

The honest tradeoffs

Trying to guess segment IDs.

Anti-pattern

A developer tries to send a mailout using an old, misspelled list tag name and gets a 404 error because the system can't find the resource. They waste time guessing valid names.

The Fix

First, call list_tags to see every available segmentation tag. Then, use that exact output when calling tools like list_subscribers or running campaigns.

Running updates manually.

Anti-pattern

A user finds out a client changed their job title and has to log into the web dashboard, find the specific contact record, and change it by hand. This process is slow and error-prone.

The Fix

Just call update_subscriber. Provide the subscriber ID and the new data fields (e.g., 'Update user 123: set Job Title to Senior Manager'). It's a single command.

Assuming campaign existence.

Anti-pattern

A user asks for metrics on 'Last Month’s big sale,' but doesn't know the exact internal mailing name, leading to an empty or irrelevant report. They waste time chasing missing data points.

The Fix

Always start by calling list_mailings first. This gives you a clean list of all valid campaign names and IDs, so you can ask for metrics on 'the Spring Newsletter' with confidence.

When It Fits, When It Doesn't

Use this server if your workflow requires deep interaction between mailing analytics, subscriber data management, and automated actions. You need to check who is subscribed (list_subscribers), what campaigns ran (list_mailings), and then perform a specific action (like send_transactional_email) based on that retrieved data.

Don't use this if you just need to view an exported CSV or manage your list outside the context of email marketing. For simple data viewing, relying solely on database queries might be enough. But when the task involves 'run a campaign,' 'segment by behavior,' or 'send a confirmation,' this MCP is essential because it connects the retrieval layer (get_subscriber) with the execution layer (trigger_automation). It's built for action-oriented marketing workflows, not just read-only reporting.

Questions you might have

How do I check campaign performance using Mailingwork MCP Server? +

Call list_mailings to get a list of all campaigns. Then, ask for the metrics on a specific ID or name. The agent pulls open rates and click data directly.

Can I update a subscriber's details using Mailingwork MCP Server? +

Yes, use update_subscriber. You provide the unique subscriber ID and specify what fields you need to change (like email or status). It updates the record in place.

What is the best way to segment my audience with Mailingwork MCP Server? +

Use list_tags first to see all available tags. Then, ask your agent to filter using those tags or use list_subscribers to build a custom list based on multiple criteria.

Does Mailingwork MCP Server handle GDPR compliance? +

Yes, the server is designed with GDPR in mind. You can check consent status and manage lists while adhering to regional privacy requirements through its tools.

How do I list all available subscriber groups using the `list_lists` tool with Mailingwork MCP Server? +

You call the list_lists tool. This command retrieves a full catalog of every mailing list you own. The output provides the unique name, ID, and current total count for each group.

What happens if I run into an error while using `send_transactional_email` with Mailingwork MCP Server? +

The server returns specific failure codes and detailed messages. Your agent reads this feedback, telling you exactly why the email failed—for instance, if the recipient address is invalid or if rate limits are hit.

Can I run complex workflows using the `trigger_automation` tool with Mailingwork MCP Server? +

Yes, this tool lets your agent activate pre-built automations. You simply pass the required trigger parameters to execute multi-step processes without writing any code.

What kind of authentication does Mailingwork MCP Server require for setup? +

The server requires your specific Mailingwork username and password credentials. Your AI client securely handles these inputs, allowing the agent to manage campaigns immediately after connection.

Can I manage campaigns and track delivery? +

Yes. Create and schedule campaigns, track opens, clicks, bounces, and monitor sender reputation.

Does Mailingwork use Basic Auth? +

Yes. Mailingwork uses HTTP Basic Auth with username and password against api.mailingwork.de/webservice/v2.

Is Mailingwork GDPR-compliant? +

Yes. Mailingwork is a German email platform built for GDPR compliance with data processing in EU data centers.

Connect to your AI in seconds.

Create subscriber

Get mailing

Get subscriber

Mailingwork MCP Server: 10 Tools for Email Marketing

Make your AI actually useful.

Create Subscriber

Get Mailing

Get Subscriber

List Lists

List Mailings

List Subscribers

List Tags

Send Transactional Email

Trigger Automation

Update Subscriber

Security and governance baked right in.

Claude AI

Open Claude Settings

Add Custom Connector

Start a conversation

Claude Code

Open your terminal

Add the MCP Server

Start coding

Cursor

One-Click Install (Recommended)

Open Cursor Settings

Add New Server

Use in Composer

Antigravity

Configure Agent Environment

Bind the Endpoint

Execute

VS Code Copilot

One-Click Install (Recommended)

Open MCP Settings

Add Server Config

Windsurf

One-Click Install (Recommended)

Open Windsurf Settings

Add Server Endpoint

LangChain

Install Dependencies

Connect the Server

CrewAI

Define the Tool

Execute Task

Choose How to Get Started

Build Your Own

Make Your AI Do More

Works with Claude, ChatGPT, Cursor, and more

Segmenting and analyzing lists shouldn't involve jumping between tabs.

Mailingwork MCP Server: Send critical emails with one command.

What your AI can actually do with this

Here's how it actually works

Who is this actually for?

What Changes When You Connect

See it in action

The quarterly review.

Onboarding new clients.

Fixing an inactive segment.

Handling an order update.

The honest tradeoffs

Trying to guess segment IDs.

Running updates manually.

Assuming campaign existence.

When It Fits, When It Doesn't

Questions you might have