VirtualSMS
    VirtualSMS
    Log in
    Codex Config · v1.1.1

    Codex Config for SMS verification

    A drop-in ~/.codex/config.toml that gives OpenAI's Codex CLI real-SIM SMS verification — no GPT Actions setup, no custom tools.

    View on GitHub
    Explore with AI:ChatGPTClaudePerplexityGeminiGrok
    Real-SIM SMS verification MCP for humans and AI agents — works with Claude, Cursor, ChatGPT, Perplexity & Gemini
    Updated:
    18 toolsv1.1.12500+ services145+ countries

    What you get

    One drop-in config that wires Codex to the VirtualSMS MCP server — six capabilities live on day one.

    Native MCP integration — Codex CLI reads MCP servers from config.toml.

    18 SMS verification tools available to every Codex session out of the box.

    Real physical SIM numbers — not VoIP — across 2500+ services and 145+ countries.

    Same VIRTUALSMS_API_KEY env var as every other client. One key, every surface.

    wait_for_code returns over WebSocket the moment the carrier delivers the SMS.

    No GPT Actions, no custom OpenAPI spec — pure MCP stdio.

    Recommended

    Quick install — Hosted MCP (HTTP)

    Zero install. Paste the block into your Codex MCP settings, plug in your VirtualSMS API key, restart.

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

    Hosted at https://mcp.virtualsms.io/mcp. Same 18 tools as the npm package, no Node required.

    Alternative: Local Node install

    Codex config file

    Prefer running stdio locally? Same backend, same auth — npm-installed instead of hosted.

    macOS / Linux~/.codex/config.toml
    Windows%USERPROFILE%\.codex\config.toml
    toml
    [mcp.servers.virtualsms]
command = "npx"
args = ["-y", "virtualsms-mcp"]
env = { VIRTUALSMS_API_KEY = "your_key_here" }

    Append the block above to your Codex config.toml (create the file if it does not exist). Restart Codex CLI. Verify with `codex --list-tools | grep virtualsms` — you should see 18 entries.

    Replace your_key_here (stdio) or vsms_your_api_key_here (HTTP) with a key from Settings → API Keys or sign up free.

    Why real SIMs (not VoIP or eSIM)

    VirtualSMS provisions physical SIM cards on operators like Vodafone, O2, T-Mobile and Lebara. Each number lives on a real handset on a real carrier. WhatsApp, Telegram, Google, Discord and 2500+ other services accept these numbers because they pass carrier_lookup checks — the API every modern verification provider runs to filter out VoIP and eSIM pools.

    VoIP numbers (Twilio, TextNow, Google Voice) and eSIM-only numbers fail those checks. The verification request bounces with a generic "this number cannot receive verification codes" error — so your Codex agent burns budget on numbers that never deliver. Every number we sell is a carrier_lookup pass before it ever lands in your order.

    That is the entire pitch: real numbers, real delivery. Verifications from $0.05, full refund if no SMS arrives.

    Compatible services

    Twelve of the most-requested verification surfaces work today through the Codex config. Plus 1,988 more on the same backend.

    Messaging
    • WhatsApp
    • Telegram
    • Discord
    • Signal
    Identity & social
    • Google
    • Instagram
    • Facebook
    • X (Twitter)
    Apps
    • TikTok
    • Snapchat
    • LinkedIn
    • Tinder
    Standalone repo

    virtualsms-io/codex-config-sms-verification

    Source, install instructions, and example Codex sessions. MIT-licensed. PRs welcome.

    Open on GitHub

    Codex FAQ

    Why TOML instead of JSON?+

    Codex CLI's config.toml is the canonical configuration surface — it controls models, providers, and MCP servers in one file. Every other MCP client uses JSON; Codex uses TOML. The package and the env var are identical.

    Does this work with the OpenAI ChatGPT app or only the Codex CLI?+

    Codex CLI only. The ChatGPT web/mobile/desktop apps do not speak MCP — they use GPT Actions, a different protocol. For ChatGPT, build a custom GPT that calls the VirtualSMS REST API directly. For Codex CLI, the config above gives you all 18 MCP tools natively.

    Which Codex CLI version is required?+

    Any version with MCP support — that's effectively every release of the open-source Codex CLI from 2025 onward. Run `codex --version` to confirm. If MCP servers do not appear, update Codex first.

    Can I run Codex with both VirtualSMS MCP and other MCP servers?+

    Yes. config.toml accepts any number of [mcp.servers.*] entries. Codex loads them all at startup and exposes the union of tools to the agent. No conflicts with other MCP servers.

    Does this cost extra on top of OpenAI usage?+

    No surcharge from VirtualSMS — activations bill from $0.05, same as every other surface. OpenAI bills tokens for the Codex session separately, as always.

    Looking for the full MCP setup across every client?

    Connect
    Main MCP pagenpm: virtualsms-mcpGitHub: virtualsms-io/mcp-serverGlama MCP directoryREST API docs

    Real-SIM SMS verification MCP for humans and AI agents — works with Claude, Cursor, ChatGPT, Perplexity & Gemini · virtualsms-mcp v1.1.1 · last updated 2026-04-25