Bring Sms Gateway
to AutoGen
Learn how to connect TNZ Communications to AutoGen 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 AutoGen?
AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use TNZ Communications tools. Connect 12 tools through Vinkius and assign role-based access. a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.
- —
Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use TNZ Communications tools to solve complex tasks
- —
Role-based architecture lets you assign TNZ Communications tool access to specific agents. a data analyst queries while a reviewer validates
- —
Human-in-the-loop support: agents can pause for human approval before executing sensitive TNZ Communications tool calls
- —
Code execution sandbox: AutoGen agents can write and run code that processes TNZ Communications tool responses in an isolated environment
TNZ Communications in AutoGen
TNZ Communications and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect TNZ Communications to AutoGen 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 AutoGen
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 AutoGen 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 AutoGen
Every tool call from AutoGen 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 AutoGen connect to MCP servers?
Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call TNZ Communications tools during their conversation turns.
Can different agents have different MCP tool access?
Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.
Does AutoGen support human approval for tool calls?
Yes. Configure human-in-the-loop mode so agents pause and request approval before executing sensitive MCP tool calls.
McpWorkbench not found
Install: pip install "autogen-ext[mcp]"