Bring Onewaysms
to CrewAI
Learn how to connect OneWaySMS 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 OneWaySMS MCP Server?
Connect your OneWaySMS account to any AI agent and take full control of your global SMS orchestration through natural conversation. OneWaySMS provides a reliable and high-speed gateway for business messaging, and this integration allows you to send standard or Unicode SMS, monitor credit balances, and track delivery statuses directly from your chat interface.
What you can do
- SMS & Messaging Orchestration — Send individual or bulk text messages programmatically to ensure your alerts and notifications are always synchronized.
- Unicode & Multilingual Support — Dispatch messages using standard ASCII or Unicode (for special characters and emojis) via natural language to reach your global audience.
- Credit & Balance Intelligence — Access and monitor your available SMS credit balance directly from the AI interface to ensure uninterrupted service.
- Transaction & Delivery Control — Retrieve real-time delivery status for any message using its unique Transaction ID (MTID) using simple AI commands.
- Operational Monitoring — Track system responses and manage regional gateway settings to ensure your communication pipeline is always optimized.
How it works
1. Subscribe to this server
2. Enter your OneWaySMS API Username and API Password from your dashboard
3. Start managing your SMS communications from Claude, Cursor, or any MCP-compatible client
No more manual logging to check if a message was delivered. Your AI acts as a dedicated messaging coordinator or operations assistant.
Who is this for?
- Operations Managers — quickly send emergency alerts and monitor credit usage without switching apps.
- Customer Success Teams — automate the delivery of status updates and track message reception via natural conversation.
- Developers — integrate real-time SMS capabilities and balance tracking directly within the chat.
Built-in capabilities (11)
Verify API connectivity
Check remaining SMS credits
Get a detailed delivery report for a message
Get current API and gateway configuration
Retrieve character limits and regional policies
Track message delivery status
List approved Alphanumeric Sender IDs
Send SMS to multiple recipients at once
Send a one-time verification code via SMS
Send a standard text message
). Limit 70 chars per credit. Send a Unicode text message
Why CrewAI?
When paired with CrewAI, OneWaySMS becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call OneWaySMS 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
OneWaySMS in CrewAI
OneWaySMS and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect OneWaySMS 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 OneWaySMS in CrewAI
The OneWaySMS 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
OneWaySMS for CrewAI
Every tool call from CrewAI to the OneWaySMS MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can my AI automatically find the delivery status for a specific SMS by its transaction ID?
Yes! Use the get_status tool with the Transaction ID (MTID). Your agent will respond with the current delivery state (e.g., Delivered, Failed, or Pending) in seconds.
How do I find my OneWaySMS API Username and Password?
Log in to your OneWaySMS dashboard, navigate to the API section, and you will find your dedicated API Username and API Password (which are different from your web login).
What is the character limit for ASCII vs Unicode messages?
Standard ASCII messages allow up to 160 characters per SMS. Unicode messages (which support special characters and emojis) are limited to 70 characters per 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.