TNZ Communications MCP Server for VS Code CopilotGive VS Code Copilot instant access to 12 tools to Check Api Health, Create Tnz Contact, Get Account Balance, and more
GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.
Ask AI about this App Connector for VS Code Copilot
The TNZ Communications app connector for VS Code Copilot is a standout in the Communication Messaging category — giving your AI agent 12 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install TNZ Communications and 3,400+ MCP Servers from a single visual interface.




{
"mcpServers": {
"tnz-communications": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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
About 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.
GitHub Copilot Agent mode brings TNZ Communications data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 12 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
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.
The TNZ Communications MCP Server exposes 12 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
All 12 TNZ Communications tools available for VS Code Copilot
When VS Code Copilot connects to TNZ Communications through Vinkius, your AI agent gets direct access to every tool listed below — spanning sms-gateway, voice-broadcasting, text-to-speech, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.
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)
Connect TNZ Communications to VS Code Copilot via MCP
Follow these steps to wire TNZ Communications into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Create MCP config
.vscode/mcp.json file in your project rootAdd the server config
Enable Agent mode
Start using TNZ Communications
Why Use VS Code Copilot with the TNZ Communications MCP Server
GitHub Copilot for Visual Studio Code provides unique advantages when paired with TNZ Communications through the Model Context Protocol.
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
TNZ Communications + VS Code Copilot Use Cases
Practical scenarios where VS Code Copilot combined with the TNZ Communications MCP Server delivers measurable value.
Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step
DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review
Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses
Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples
Example Prompts for TNZ Communications in VS Code Copilot
Ready-to-use prompts you can give your VS Code Copilot agent to start working with TNZ Communications immediately.
"Send a SMS to +6421000000: 'The delivery is arriving at 2 PM today.'"
"What is the status of my message ID 'ref_123'?"
"Check my current TNZ account balance."
Troubleshooting TNZ Communications MCP Server with VS Code Copilot
Common issues when connecting TNZ Communications to VS Code Copilot through the Vinkius, and how to resolve them.
MCP tools not available
TNZ Communications + VS Code Copilot FAQ
Common questions about integrating TNZ Communications MCP Server with VS Code Copilot.
Which VS Code version supports MCP?
How do I switch to Agent mode?
Can I restrict which MCP tools Copilot can access?
Does MCP work in VS Code Remote or Codespaces?
.vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.