2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 10 Tools Framework

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

Vinkius supports streamable HTTP and SSE.

python
from crewai import Agent, Task, Crew

agent = Agent(
    role="Cordial Specialist",
    goal="Help users interact with Cordial effectively",
    backstory=(
        "You are an expert at leveraging Cordial 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 Cordial "
        "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)
Cordial
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 Cordial MCP Server

Integrate Cordial, the cross-channel marketing platform, directly into your AI workflow. Manage your audience segments, trigger automated messages, and monitor campaign performance using natural language.

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

  • Audience Management — List and search for subscribers, and update profile attributes seamlessly.
  • Campaign Monitoring — Track the performance of batch and transactional email/SMS campaigns.
  • Automation Control — Monitor and manage active message automation workflows.
  • Data Insights — Access supplementary data collections and account metadata via chat.

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

Follow these steps to integrate the Cordial MCP Server with CrewAI.

01

Install CrewAI

Run pip install crewai

02

Replace the token

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

03

Customize the agent

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

04

Run the crew

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

Why Use CrewAI with the Cordial MCP Server

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

01

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

02

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

03

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

04

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

Cordial + CrewAI Use Cases

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

01

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

02

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

03

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

04

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

Cordial MCP Tools for CrewAI (10)

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

01

get_account_details

Resolves system-level account identifiers, plan configuration, and core platform settings. Get metadata about your Cordial account

02

get_subscriber_profile

Resolves granular profile data including custom attributes, device tokens, and list memberships. Get full profile and attributes for a subscriber

03

list_audience_segments

Resolves list identity properties such as segment IDs, names, and subscriber counts. List contact segments and audience groups

04

list_automation_messages

Resolves active automated message definitions and workflow status for triggered communications. List active automated message workflows

05

list_contacts

Resolves contact identity properties including email addresses, channel opt-ins, and attribute metadata across the Cordial system boundary. List subscribers in Cordial

06

list_marketing_campaigns

Resolves campaign identity and status, including scheduling data and high-level performance indicators. List marketing campaigns and their performance

07

list_messages

Resolves batch and transactional message definitions, including templates, subject lines, and sender profiles. List batch and transactional messages

08

list_supplementary_data

Resolves metadata for custom data collections used for message personalization. List supplement collections (external data tables)

09

search_campaigns_by_name

Resolves a subset of campaigns matching the name criteria across the platform boundary. Search for marketing campaigns by name

10

upsert_subscriber

Creates or updates a profile with identity properties, channel preferences, and custom attributes. Create or update a subscriber profile

Example Prompts for Cordial in CrewAI

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

01

"List the most recent marketing campaigns and their open rates."

02

"Show me the profile for the subscriber 'user@example.com'."

03

"Check the size of our 'Active Customers' list."

Troubleshooting Cordial MCP Server with CrewAI

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

01

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

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.

Cordial + CrewAI FAQ

Common questions about integrating Cordial MCP Server with CrewAI.

01

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.
02

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.
03

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.
04

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.
05

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.

Connect Cordial to CrewAI

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.