Bring Sms Gateway
to CrewAI
Learn how to connect TNZ Communications 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 TNZ Communications MCP Server?
Empower your AI agent with access to the TNZ Group messaging gateway to automate your SMS, Voice, and Fax communications in New Zealand and globally.
What you can do
- Multichannel Messaging — Send SMS, automated voice calls (Text-to-Speech), and digital faxes programmatically.
- Delivery Oversight — Monitor the real-time status of sent messages and retrieve incoming SMS replies.
- Contact & Group Control — Manage your TNZ address book and organize contacts into groups for broadcast messaging.
- Operational Monitoring — Track your account credit balance and retrieve detailed messaging usage and cost reports.
How it works
1. Subscribe to this server
2. Enter your TNZ Auth Token from your dashboard
3. Start communicating from Claude, Cursor, or any MCP client
Who is this for?
- Business Operations — Quickly send notifications and alerts to staff or customers via natural conversation.
- Marketing Teams — Automate SMS and Voice outreach sequences and track engagement results.
- Customer Support — Monitor and respond to incoming SMS replies without leaving your workspace.
Built-in capabilities (12)
Verify TNZ API connectivity
Add a new contact to TNZ
Check account credit balance
Check delivery status of a message
Retrieve usage and cost reports
List your contact groups
List saved message templates
List inbound SMS replies
List saved contacts in TNZ
Send a document as a fax
Send an SMS message
Send a voice call (Text-to-Speech)
Why CrewAI?
When paired with CrewAI, TNZ Communications becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call TNZ Communications 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
TNZ Communications in CrewAI
TNZ Communications and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect TNZ Communications 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 TNZ Communications in CrewAI
The TNZ Communications 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
TNZ Communications for CrewAI
Every tool call from CrewAI to the TNZ Communications 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 get an Auth Token for TNZ?
Log in to your TNZ Dashboard, go to Users, select your user, and click the API tab to generate your unique Auth Token.
Can the agent send voice calls?
Yes, using the send_tts_voice_call tool, the agent can convert text into a high-quality voice call for your recipients.
Does this support sending faxes?
Absolutely. The send_digital_fax tool allow you to send documents or text as faxes directly from 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.