Bring Cpaas
to CrewAI
Learn how to connect Authkey to CrewAI and start using 13 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Authkey MCP Server?
Connect your Authkey.io account to any AI agent and take full control of your multi-channel communication and automated notification workflows through natural conversation.
What you can do
- Multichannel Messaging Orchestration — Instantly dispatch high-fidelity SMS, transactional emails, and voice alerts to customers worldwide using a single unified interface
- Security & OTP Intelligence — Programmatically send and verify One-Time Passwords (OTPs) to build secure authentication and 2FA flows directly through your agent
- Voice Automation Architecture — Initiate automated voice calls with high-fidelity Text-to-Speech (TTS) or pre-defined templates for critical security alerts
- Template Management — Access and monitor your complete directory of communication templates (SMS/Email) to ensure perfectly coordinated brand messaging
- Financial Visibility Monitoring — Access real-time balance data across all channels (SMS, Voice, Email) directly through your agent for instant operational reporting
How it works
1. Subscribe to this server
2. Retrieve your API Key from the Authkey dashboard at authkey.io
3. Start automating your global notifications and engagement from Claude, Cursor, or any MCP client
No more manual toggling between messaging portals or managing multiple protocol integrations. Your AI acts as your dedicated CPaaS engineer and communication coordinator.
Who is this for?
- Customer Support Teams — instantly send order updates and verification codes using natural language commands
- Security Engineers — integrate high-speed 2FA and OTP verification into custom bots and internal tools
- Marketing Leads — automate the dispatch of omnichannel campaigns and monitor credit usage through simple AI queries
Built-in capabilities (13)
Verify connectivity
Check balance
Get email status
Get SMS status
Get voice call status
List SMS history
List templates
Send bulk SMS
Send an email
Send OTP
Send an SMS
Send a voice call
Verify OTP
Why CrewAI?
When paired with CrewAI, Authkey becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Authkey 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
Authkey in CrewAI
Authkey and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Authkey 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 Authkey in CrewAI
The Authkey 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 13 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
Authkey for CrewAI
Every tool call from CrewAI to the Authkey MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Authkey API Key?
Log in to your account at authkey.io, navigate to the dashboard, and copy your unique Authkey.
Can I verify OTPs via AI?
Yes! The verify_otp tool allows your agent to confirm security codes by providing the Log ID from the original request and the code entered by the user.
How do I check my remaining credits?
Use the check_balance tool to retrieve high-fidelity real-time credit status for SMS, Voice, and Email channels directly through your agent.
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.