Sms

VirtualSMS MCP Server

Quick links: Quickstart · Why VirtualSMS · What you can build · Tools · Questions · Examples · Changelog · Security policy · Status

VirtualSMS is an account verification platform for developers and AI agents. It combines one-time SMS verification, dedicated number rentals, matching-country proxies and private cloud browser sessions behind one API, one MCP server and one prepaid balance.

Infrastructure for AI agents that need real-world phone verification.

The numbers are carrier-issued mobile numbers, backed by real physical SIM cards on carrier networks, not VoIP, which is why they pass the line-type checks that reject VoIP numbers at signup.

From one prepaid balance you can:

• receive one-time SMS codes from $0.05
• rent dedicated numbers from 1 to 30 days
• buy matching-country residential, mobile and datacenter proxies
• launch private cloud browser sessions that work alongside your number and proxy (beta)

All four work together from one prepaid balance, one API and one dashboard. Use only the pieces you need, or combine them into a single verification workflow.

Most providers solve one piece of the verification workflow. VirtualSMS combines numbers, rentals, proxies and cloud browser sessions behind one API, SDKs and an MCP server, so you use only the pieces you need or combine them into one workflow.

VirtualSMS can be used by individuals manually, integrated into applications with SDKs and APIs, or driven by AI agents through MCP. Use the platform through a REST API, official SDKs for Node, Python, PHP, Ruby and .NET, a hosted MCP server, or automation tools like n8n.

This server exposes that platform to any MCP client. Built for AI agents. Designed for AI-agent workflows. Works with Claude Code, Claude Desktop, Cursor, Windsurf and every MCP-compatible client, with no wrapper code to write.

---

Quickstart

Paste this into your MCP client's config. Nothing to install, no Node.js required on the client:

{

"mcpServers": { "virtualsms": { "type": "streamableHttp", "url": "https://mcp.virtualsms.io/mcp", "headers": { "x-api-key": "vsms_your_api_key_here" } } } }

Get an API key at virtualsms.io. Then ask your agent:

"Buy me a Telegram number in the cheapest country and wait for the code."

Prefer to run it locally over stdio instead:

npx virtualsms-mcp

---

Why VirtualSMS

Verifying an account should not mean stitching together numbers from one provider, proxies from another, and browser sessions from a third: multiple accounts, multiple balances and APIs, and support spread across vendors. VirtualSMS brings those pieces together behind one balance, one API and one MCP server.

VirtualSMS combines all three under one account, and gives you one way to drive them:

• Carrier-issued mobile numbers. Backed by real physical SIM cards, not VoIP, so they resolve as mobile at signup.
• Matching-country proxies. Residential, mobile and datacenter pools, so the number and the IP agree.
• Private cloud browser sessions. Beta.
• REST API. Documented at virtualsms.io/docs.
• Hosted MCP server. This repo, live at https://mcp.virtualsms.io/mcp.
• One prepaid balance. Verification, rentals and proxies all draw from it.

Everything below expands on those six.

---

What you can build

Concrete jobs this server does today. Every one is a plain-English request your agent turns into tool calls:

Runnable versions of the first two live in examples/.

---

Client setup

Every client runs the same npx virtualsms-mcp stdio command. Only the file location and format differ. The hosted config above works anywhere streamableHttp is supported and is the recommended path.

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{

"mcpServers": { "virtualsms": { "command": "npx", "args": ["virtualsms-mcp"], "env": { "VIRTUALSMS_API_KEY": "vsms_your_api_key_here" } } } }

Quit and reopen Claude Desktop. A drop-in config plus a worked transcript lives in examples/03-claude-desktop-config/.

Claude Code, Cursor, Windsurf, OpenClaw, Codex, Hermes, Cline, Zed, Continue.dev

Claude Code (CLI)

claude mcp add --scope user virtualsms npx virtualsms-mcp -e VIRTUALSMS_API_KEY=vsms_your_api_key_here

Cursor

Edit ~/.cursor/mcp.json:

{

"mcpServers": { "virtualsms": { "command": "npx", "args": ["virtualsms-mcp"], "env": { "VIRTUALSMS_API_KEY": "vsms_your_api_key_here" } } } }

Windsurf

Edit ~/.codeium/windsurf/mcp_config.json:

{

"mcpServers": { "virtualsms": { "command": "npx", "args": ["virtualsms-mcp"], "env": { "VIRTUALSMS_API_KEY": "vsms_your_api_key_here" } } } }

OpenClaw

Edit ~/.openclaw/mcp.json:

{

"mcpServers": { "virtualsms": { "command": "npx", "args": ["virtualsms-mcp"], "env": { "VIRTUALSMS_API_KEY": "vsms_your_api_key_here" } } } }

Codex (OpenAI Codex CLI)

Edit ~/.codex/config.toml:

[mcp_servers.virtualsms]

command = "npx" args = ["virtualsms-mcp"] env = { VIRTUALSMS_API_KEY = "vsms_your_api_key_here" }

Hermes

Edit your Hermes MCP config:

{

"mcpServers": { "virtualsms": { "command": "npx", "args": ["virtualsms-mcp"], "env": { "VIRTUALSMS_API_KEY": "vsms_your_api_key_here" } } } }

Cline (VS Code)

Open the Cline MCP settings panel and add:

{

"virtualsms": { "command": "npx", "args": ["virtualsms-mcp"], "env": { "VIRTUALSMS_API_KEY": "vsms_your_api_key_here" } } }

Zed

Edit ~/.config/zed/settings.json:

{

"context_servers": { "virtualsms": { "command": { "path": "npx", "args": ["virtualsms-mcp"], "env": { "VIRTUALSMS_API_KEY": "vsms_your_api_key_here" } } } } }

Continue.dev

Edit ~/.continue/config.yaml:

mcpServers:

• name: virtualsms command: npx args:
• virtualsms-mcp env: VIRTUALSMS_API_KEY: vsms_your_api_key_here

Does this work with ChatGPT?

Yes, via ChatGPT's Developer Mode. Open Settings, turn on Developer mode, then add https://mcp.virtualsms.io/mcp as a custom connector (Plus, Pro, Business, Enterprise and Edu plans; not available on the free tier). Setup is a URL paste rather than a config file, so it differs from the client setups above. ChatGPT only connects to remote MCP servers over SSE or streaming HTTP, so use the hosted endpoint, not the local stdio command. The REST API is still there if you would rather build a custom GPT or Action instead.

---

Configuration

---

Tools

40 tools by default. Set VIRTUALSMS_ENABLE_SESSIONS=1 to expose 3 more.

Tool names are shown below without the virtualsms_ prefix for readability. The real wire names are prefixed: virtualsms_create_order, virtualsms_get_sms, and so on.

Activation and account (18 tools)

The core SMS verification surface: discover a service, price it, buy a number, get the code.

`get_sms` vs `wait_for_sms`: wait_for_sms is the recommended default for interactive agent workflows. It blocks and returns the moment the SMS arrives over WebSocket. Use get_sms