MCP server setup for AI agents (Claude Desktop, Cursor)

The Model Context Protocol (MCP) server lets your AI agent — Claude Desktop, Cursor, Claude Code, or any MCP-compatible client — drive the verification flow directly. Once configured with your VirtualSMS Bearer token, the agent can list services, pick a country, place an order, poll for the SMS, extract the code, and submit it to whatever platform you’re signing up to — all without you in the loop.

When to use the MCP server

• Agentic onboarding flows — your AI signs your customers up to other services and needs phone verification along the way.
• Account farms managed by AI — create + maintain multiple accounts across platforms with an agent handling the verification step.
• Multi-step workflows where the agent orchestrates several apps, each needing its own SMS verification.

Quick start — 3 steps

1. Grab your Bearer token from Settings → API in your VirtualSMS dashboard.
2. Configure your MCP client — for Claude Desktop, edit claude_desktop_config.json; for Cursor, edit .cursor/mcp.json. Add the VirtualSMS MCP server with your Bearer token.
3. Restart your client. The agent should now have access to 18 VirtualSMS tools — list services, get pricing, create orders, poll for SMS, cancel, refund.

Full setup — copy-paste config

The complete setup with copy-paste configs for every supported client (Claude Desktop, Cursor, Claude Code, OpenAI Agents SDK, custom MCP clients), tool reference, error codes, and example agent prompts lives in our developer docs.

Common questions

• Is the MCP server free? Yes — the server itself is free to use. You pay for the verifications your agent buys.
• Can multiple agents share a token? Yes, but rate-limits apply (120 req/min default). Contact support for higher limits if you run a fleet.
• Self-hosted vs hosted? Both. The hosted MCP server is the default (zero setup). Source code for self-hosting lives at github.com/virtualsms-io/mcp-server.