Bring Sms Notifications
to CrewAI
Learn how to connect CM.com to CrewAI and start using 11 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the CM.com MCP Server?
Connect your CM.com account to any AI agent and control your omnichannel communications through natural conversation.
What you can do
- SMS Messaging — Send individual SMS messages or broadcast to multiple recipients in a single request
- Rich Messaging — Deliver messages through WhatsApp, Viber, RCS, or Apple Messages for Business
- WhatsApp Templates — Send pre-approved WhatsApp Business template messages with namespace support
- Voice Communications — Place automated calls for voice OTP delivery or text-to-speech notifications
- Email Delivery — Send HTML emails through CM.com's delivery infrastructure
- OTP Verification — Send SMS OTPs and verify codes for two-factor authentication
- Account Management — Check your credit balance and list virtual phone numbers
How it works
1. Subscribe to this server
2. Enter your CM.com Product Token from your Channels dashboard
3. Start sending messages from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Operations Teams — send transactional SMS, WhatsApp notifications, and voice alerts without writing integration code
- Security Teams — implement OTP verification flows for two-factor authentication directly from AI workflows
- Marketing Teams — send bulk SMS campaigns and check delivery through conversational AI
Built-in capabilities (11)
com account. Check account balance
com account. List phone numbers
Send bulk SMS
com email delivery infrastructure. Send an email
Send OTP via SMS
Send a rich message
Send an SMS
Send voice notification
Send voice OTP
Send WhatsApp template
Verify OTP code
Why CrewAI?
When paired with CrewAI, CM.com becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call CM.com 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
CM.com in CrewAI
CM.com and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect CM.com 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 CM.com in CrewAI
The CM.com 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 11 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
CM.com for CrewAI
Every tool call from CrewAI to the CM.com 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 messages through WhatsApp, Viber, and other rich channels?
Yes! The send_rich_message action lets you send through WhatsApp, Viber, RCS, or Apple Messages by specifying the channel parameter. For WhatsApp Business specifically, use send_whatsapp to send pre-approved template messages with a template ID and namespace.
Can I implement two-factor authentication with OTP verification?
Yes. Use send_otp_sms to deliver a verification code via SMS — it returns a verification ID. Then call verify_otp with that verification ID and the code the user enters. For voice-based OTP delivery, use send_voice_otp to read the code to the user via an automated phone call.
Can I check my CM.com credit balance before sending campaigns?
Yes. The get_balance tool retrieves your current credit balance. Use list_numbers to see all virtual phone numbers in your account. Both tools help you plan campaigns before committing to bulk sends via send_bulk_sms.
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.