Can I check the statistics for a specific campaign using the agent?

Yes! Use the `get_campaign_performance` tool with the Campaign ID. Your agent will fetch the detailed performance data, including open rates, clicks, and bounces, directly from Campaign Monitor.

How do I add a new subscriber to a list?

Simply ask the agent to `add_subscriber` and provide the List ID, name, and email address. The subscriber will be added to your Campaign Monitor list with consent tracking enabled automatically.

Does the integration allow listing all my clients?

Yes. Use the `list_clients` tool. It will retrieve all the client accounts managed under your Campaign Monitor account, making it easy to find the IDs needed for other operations.

Campaign Monitor MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Campaign Monitor
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Campaign Monitor through Vinkius, pass the Edge URL in the `mcps` parameter and every Campaign Monitor tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Campaign Monitor Specialist",
    goal="Help users interact with Campaign Monitor effectively",
    backstory=(
        "You are an expert at leveraging Campaign Monitor tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Campaign Monitor "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Campaign Monitor MCP Server

Connect your Campaign Monitor account to any AI agent and orchestrate your email marketing, subscriber management, and multi-channel campaigns through natural conversation.

When paired with CrewAI, Campaign Monitor becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Campaign Monitor tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Subscriber Oversight — List all your active subscribers and retrieve detailed profiles, including contact information and history.
Campaign Management — List all email campaigns and retrieve detailed metadata, including subjects and statuses.
Performance Tracking — Retrieve real-time statistics for specific campaigns to monitor engagement, ROI, and delivery rates.
List Coordination — Access and list your contact lists and segments to ensure your audience is properly managed.
Client & account Monitoring — Access core client information and templates managed within the platform.
Subscriber Growth — Add new subscribers directly from your workspace with custom names and automated consent tracking.

The Campaign Monitor MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Campaign Monitor to CrewAI via MCP

Follow these steps to integrate the Campaign Monitor MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from Campaign Monitor

Why Use CrewAI with the Campaign Monitor MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Campaign Monitor through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Campaign Monitor + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Campaign Monitor MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Campaign Monitor for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Campaign Monitor, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Campaign Monitor tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Campaign Monitor against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Campaign Monitor MCP Tools for CrewAI (10)

These 10 tools become available when you connect Campaign Monitor to CrewAI via MCP:

add_subscriber

Add a new subscriber to a list

get_account_info

Retrieve core account information

get_campaign_performance

Retrieve performance summary for a specific campaign

get_client_details

Get details of a specific client

get_contact_list

Get details of a specific contact list

list_campaigns

List all campaigns for a client

list_clients

List all client accounts

list_contact_lists

List all contact lists for a specific client

list_email_templates

List all templates for a client

list_subscribers

List active subscribers in a list

Example Prompts for Campaign Monitor in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Campaign Monitor immediately.

"List all my clients in Campaign Monitor."

"Show the lists for client cli_123."

"Add Jane Smith (jane@example.com) to the 'Weekly Newsletter' list."

Troubleshooting Campaign Monitor MCP Server with CrewAI

Common issues when connecting Campaign Monitor to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Campaign Monitor + CrewAI FAQ

Common questions about integrating Campaign Monitor MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.