Bring Transactional Email
to CrewAI
Learn how to connect UniOne to CrewAI and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the UniOne MCP Server?
Connect your UniOne email delivery account to any AI agent and simplify how you manage your transactional messaging, email templates, and delivery tracking through natural conversation.
What you can do
- Email Delivery — Send individual or bulk transactional emails with full HTML support and personalized sender details.
- Template Automation — List, create, and send emails using pre-defined templates for consistent branding.
- Event Monitoring — Configure webhooks and track delivery events (opened, clicked, delivered) in real-time.
- Reputation Management — List and manage suppressed email addresses (unsubscribes/bounces) to protect your sender score.
- Technical Control — Fetch detailed metadata for templates and webhooks directly from the agent.
How it works
1. Subscribe to this server
2. Enter your UniOne API Key and select your Region (eu1 or us1)
3. Start managing your transactional emails from Claude, Cursor, or any MCP client
Who is this for?
- Developers & DevOps — quickly test email sending and verify template rendering via simple AI commands.
- Marketing Operations — monitor email performance and manage suppression lists directly from the workspace.
- Product Teams — automate the creation of notification templates and track user engagement metrics.
Built-in capabilities (12)
Delete a template
Delete a webhook
Get template details
Get webhook details
List suppressed emails
List email templates
List webhooks
Send a transactional email
Send email using a template
Add email to suppression list
Create or update a template
Configure a webhook
Why CrewAI?
When paired with CrewAI, UniOne becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call UniOne tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
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
mcpsparameter 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
UniOne in CrewAI
UniOne and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect UniOne to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for UniOne in CrewAI
The UniOne 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. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
UniOne for CrewAI
Every tool call from CrewAI to the UniOne MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I send an email using an existing template ID?
Yes! Use the send_template tool. Provide the Template ID and an array of recipient objects (with their email addresses) to trigger the delivery instantly.
How do I see which email addresses have been suppressed?
Run the list_suppression query. The agent will retrieve a list of unsubscribed or bounced email addresses managed by your UniOne account.
Is it possible to update an email template via AI?
Absolutely. Use the set_template action. You can provide the ID, name, subject, and the new HTML body to save changes to your template library.
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.
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.