How do I get a Courier Auth Token?

Log in to your Courier dashboard, navigate to **Settings > API Keys**, and you will find your Auth Token there. Use the 'Published' key for production environments.

What channels are supported?

Courier supports dozens of providers for Email (SendGrid, Mailgun), SMS (Twilio, MessageBird), Push (Firebase, OneSignal), and Chat (Slack, Discord).

Can I track if a message was opened?

Yes, the agent can use the get_message_details tool to check the status of a specific message, which includes tracking events like 'OPENED' or 'CLICKED' if supported by the provider.

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

Name: Courier
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

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

Integrate Courier, the smart notification infrastructure, directly into your AI workflow. Design, orchestrate, and send messages across email, SMS, push, and chat apps using natural language.

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

Send Notifications — Trigger complex notification workflows to any recipient via the Send API.
Message Monitoring — List sent messages and track their real-time delivery status (sent, delivered, opened).
Template Management — Browse available notification templates and custom brands.
Audience & User Insights — Manage subscription lists and retrieve user profiles.

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

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

Why Use CrewAI with the Courier MCP Server

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

Courier + CrewAI Use Cases

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

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

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

Courier MCP Tools for CrewAI (10)

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

get_message_details

Touches delivery logs, provider responses, and rendering metadata boundary. Get details for a specific message by ID

get_message_history

Resolves event types (SENT, DELIVERED, etc.) and detailed provider logs. Get the delivery history logs for a message

get_user_profile

Resolves contact details (email, phone) and channel-specific delivery preferences. Get the profile data for a specific user

list_audiences

Resolves audience IDs, names, and filter criteria used for segmentation. List saved audiences for targeted notifications

list_brands

Resolves brand names, colors, and logo settings used for white-labeling notifications. List custom brands configured in Courier

list_messages

Resolves message IDs, recipient identifiers, status (SENT, DELIVERED, OPENED, CLICKED), and timestamps. List sent messages and their current status

list_subscription_lists

Resolves list IDs, names, and subscriber counts. List subscription lists for managing recipients

list_templates

Resolves template names, IDs, and supported channels. List available notification templates

list_users

Resolves user IDs, roles, and account association details. List users registered in the Courier workspace

send_notification

Touches recipient profile, template engine, and multi-channel provider boundaries. Send a notification to a recipient

Example Prompts for Courier in CrewAI

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

"Check the delivery status of the last message sent to 'user@example.com'."

"Send a 'Welcome' notification to the new user with ID 'user_123'."

"List all notification templates available in my account."

Troubleshooting Courier MCP Server with CrewAI

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

Courier + CrewAI FAQ

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