How do I get Emarsys API credentials?

Log in to your Emarsys account, navigate to **Admin > Web Services**, and you can create or retrieve your **API Username** and **Secret Key**. Ensure the user has the required permissions for the resources you wish to access.

What authentication method does this integration use?

This integration uses **W-SSE authentication**, which is the standard for the Emarsys API. It requires both your API Username and Secret Key to securely generate request headers.

Can the agent trigger automation programs?

This integration currently focuses on listing and auditing programs and events. Triggering specific automation workflows should be managed via external events in the Emarsys dashboard or dedicated transactional API calls.

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

Name: Emarsys
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Emarsys through Vinkius, pass the Edge URL in the `mcps` parameter and every Emarsys 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="Emarsys Specialist",
    goal="Help users interact with Emarsys effectively",
    backstory=(
        "You are an expert at leveraging Emarsys 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 Emarsys "
        "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 Emarsys MCP Server

Integrate Emarsys, the comprehensive customer engagement platform, directly into your AI workflow. Manage your email marketing campaigns and contact lists, track audience segments and automation programs, monitor trigger events and registration forms, and oversee your omnichannel engagement using natural language.

When paired with CrewAI, Emarsys becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Emarsys 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

Campaign Oversight — List and retrieve detailed information, subject lines, and launch statuses for all your email campaigns.
Contact Intelligence — Monitor marketing contact lists and audience segments, resolving structural details and filter criteria.
Automation Management — Access and monitor automation programs and workflows, tracking active statuses and trigger events.
Engagement Auditing — Retrieve high-level summaries of campaign volume, list activity, and organizational marketing health instantly.

The Emarsys 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 Emarsys to CrewAI via MCP

Follow these steps to integrate the Emarsys 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 Emarsys

Why Use CrewAI with the Emarsys MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Emarsys 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

Emarsys + CrewAI Use Cases

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

Automated multi-step research: a reconnaissance agent queries Emarsys 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 Emarsys, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Emarsys 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 Emarsys against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Emarsys MCP Tools for CrewAI (10)

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

get_campaign_details

Get detailed settings and status for a specific email campaign

get_contact_list_details

Get detailed settings for a specific contact list

get_emarsys_account_metadata

Retrieve metadata and settings for your Emarsys account

list_audience_segments

List all audience segments (filters) in your account

list_automation_programs

List all automation programs and workflows

list_email_campaigns

List all email campaigns in your Emarsys account

list_marketing_contact_lists

List all contact lists configured in your organization

list_registration_forms

List all subscription and registration forms

list_trigger_events

List all external events used for triggering automation programs

quick_engagement_volume_audit

Retrieve a high-level summary of campaigns, lists, and automation programs

Example Prompts for Emarsys in CrewAI

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

"List all active email campaigns."

"Show me the audience segments in my account."

"What automation programs are currently running?"

Troubleshooting Emarsys MCP Server with CrewAI

Common issues when connecting Emarsys 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.

Emarsys + CrewAI FAQ

Common questions about integrating Emarsys 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.