Bring Multi Channel Messaging
to VS Code Copilot
Learn how to connect Termii to VS Code Copilot and start using 6 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Termii MCP Server?
Connect your Termii account to any AI agent and simplify how you manage your global messaging, secure verification, and multi-channel engagement through natural conversation.
What you can do
- Multi-channel Messaging — Send standard SMS and WhatsApp messages to recipients worldwide with reliable delivery tracking.
- Secure Verification (OTP) — Send and verify one-time passwords (OTP) programmatically to secure your user onboarding and transactions.
- Sender ID Management — List all registered Sender IDs to ensure your messages are delivered with recognized branding.
- Financial Monitoring — Check your account balance and track credit usage for your messaging campaigns directly from the agent.
- Global Coverage — Reach users across different channels (SMS, WhatsApp, Voice) using Termii's unified communication infrastructure.
- Real-time Oversight — Monitor transaction statuses and verify identity tokens instantly via AI commands.
How it works
1. Subscribe to this server
2. Enter your Termii API Key (found in your account dashboard)
3. Start managing your communications and verification from Claude, Cursor, or any MCP client
Who is this for?
- Developers & DevOps — quickly test messaging delivery and integrate OTP verification via simple AI commands.
- Marketing Teams — automate proactive outreach and monitor credit balances directly from the workspace.
- Security Analysts — verify identity tokens and monitor communication flows via the AI assistant.
Built-in capabilities (6)
Check account balance
List all registered Sender IDs
Pass options in JSON. Send a one-time password
Pass data as a JSON string. Send an SMS message
Pass data as a JSON string. Send a WhatsApp message
Verify an OTP code
Why VS Code Copilot?
GitHub Copilot Agent mode brings Termii data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 6 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
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
Termii in VS Code Copilot
Termii and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Termii to VS Code Copilot 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 Termii in VS Code Copilot
The Termii 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 6 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot 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
Termii for VS Code Copilot
Every tool call from VS Code Copilot to the Termii 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 an OTP code for user verification via AI?
Yes! Use the send_otp action. Provide the destination number, your Sender ID, and the message type in the JSON payload. Your agent will trigger the OTP delivery instantly.
How do I check my remaining account balance?
Run the check_balance query. The agent will retrieve your current available credits directly from Termii, helping you monitor your messaging budget.
Is it possible to see my registered Sender IDs via AI?
Absolutely. Use the list_sender_ids tool. Your agent will retrieve the complete list of all Sender IDs authorized for your account.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .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.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.