What is a sender ID and why do I need one?

A sender ID is the alphanumeric label (3-11 characters) that appears as the sender on the recipient's phone. Approved sender IDs help increase trust and open rates for your messages.

Can I receive replies to my SMS messages?

Yes! Use the `list_responses` tool to retrieve any incoming messages from your customers. This allows your agent to handle two-way communication workflows.

How do I ensure my SMS is delivered at a specific time?

When using the `send_sms` tool, provide a YYYY-MM-DD HH:MM:SS string in the `date` parameter. AvoSMS will queue the message and deliver it exactly at the requested time.

AvoSMS MCP Server for VS Code Copilot 11 tools — connect in under 2 minutes

Name: AvoSMS
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 11 Tools IDE

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.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install AvoSMS and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "avosms": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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 AvoSMS MCP Server

Orchestrate your global mobile communication with AvoSMS, the high-performance messaging platform designed for scale. By connecting AvoSMS to your AI agent, you transform SMS outreach from a manual task into a natural conversation. Your agent can now send instant notifications, schedule future broadcasts, manage approved sender identities, and audit your contact lists without you ever touching a dashboard. Whether you're tracking customer responses or monitoring credit balances, your agent acts as a real-time mobile operations manager for your business.

GitHub Copilot Agent mode brings AvoSMS data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 11 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Precision Messaging — Send individual or scheduled SMS messages globally with full support for custom delivery timestamps.
Identity Control — Request, list, and manage approved Sender IDs (names) to ensure your brand is always recognized.
Contact Orchestration — Create and manage dedicated contact lists, adding recipients dynamically via natural language.
Response Auditing — Retrieve and list incoming SMS responses to maintain a two-way dialogue with your audience.
Account Health — Instantly check your remaining credit balance and verify account connectivity on the fly.

The AvoSMS MCP Server exposes 11 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.

How to Connect AvoSMS to VS Code Copilot via MCP

Follow these steps to integrate the AvoSMS MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using AvoSMS

Ask Copilot: "Using AvoSMS, help me...". 11 tools available

Why Use VS Code Copilot with the AvoSMS MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with AvoSMS 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

AvoSMS + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the AvoSMS 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

AvoSMS MCP Tools for VS Code Copilot (11)

These 11 tools become available when you connect AvoSMS to VS Code Copilot via MCP:

add_contact

Add a contact to a list

create_list

Create a new contact list

create_sender

Request a new sender ID

delete_list

Delete a contact list

delete_sender

Delete a sender ID

get_account_check

Verify AvoSMS account connection

get_balance

Check remaining SMS credits balance

list_lists

List all contact lists

list_responses

List incoming SMS responses

list_senders

List all approved sender IDs

send_sms

Send an SMS message

Example Prompts for AvoSMS in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with AvoSMS immediately.

"Send an SMS to +33600000000 saying 'Your order is ready for pickup!' using sender 'ShopAlert'."

"Check my AvoSMS credit balance and list recent replies."

"Add the phone number +123456789 to my 'VIP Customers' list."

Troubleshooting AvoSMS MCP Server with VS Code Copilot

Common issues when connecting AvoSMS to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

AvoSMS + VS Code Copilot FAQ

Common questions about integrating AvoSMS MCP Server with VS Code Copilot.

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.