Codex Config v1.3.1

Codex Config for SMS verification

Drop-in Codex config for a full account verification workflow: real-SIM numbers, rentals, matching-country proxies and cloud browser sessions. No GPT Actions.

40 tools 2500+ services 145+ countries from $0.05 Real SIMs, not VoIP Matching-country proxies

TL;DR

Account verification for Codex: SMS, rentals, proxies and cloud browser, one prepaid balance.

Show full summary

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.

From one prepaid balance you can:

  • receive one-time SMS verification codes from $0.05
  • rent dedicated numbers for 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)

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.

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.

40 tools available to every Codex session out of the box: SMS verification, number rentals, matching-country proxies and cloud browser sessions.

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_sms 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.

toml
[mcp_servers.virtualsms]
url = "https://mcp.virtualsms.io/mcp"
http_headers = { "x-api-key" = "vsms_your_api_key_here" }

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

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 40 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 carrier-issued mobile numbers?

The numbers are carrier-issued mobile numbers, backed by real physical SIM cards on operators like Vodafone, O2 and T-Mobile, not VoIP, so they pass the line-type checks that reject VoIP at signup. 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 and eSIM-only numbers fail those checks and bounce at signup, so your Codex agent never wastes budget on a number that cannot deliver.

That is the entire pitch: real numbers, real delivery. Verifications from $0.05, full refund if no SMS arrives. The same MCP server also rents numbers for 1 to 30 days, sells matching-country proxies, and runs private cloud browser sessions (beta), all from the same balance.

Common verification services

Twelve of the most-requested verification surfaces work today through the Codex config, out of 2500+ supported services 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-sms-verification

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

Open on GitHub

Talk to Codex naturally

Type these straight into Codex, no tool names required.

  • Buy the cheapest Telegram number and wait for the code
  • Rent me a UK number for seven days
  • Find a residential proxy in Germany
  • Wait for the SMS and return only the code
  • Swap this number for a fresh one
  • Show my balance

FAQ

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?

This page is for Codex CLI. ChatGPT supports MCP via Developer Mode custom connectors (hosted MCP, streamable-HTTP/SSE, plan-gated to Plus/Pro/Business/Enterprise): add https://mcp.virtualsms.io/mcp as a connector. For Codex CLI, the config above gives you all 40 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.

Does the Codex config also give me rentals and proxies, or only SMS codes?

The same config.toml block loads the full VirtualSMS platform: one-time SMS verification, dedicated number rentals (1 to 30 days), matching-country proxies, and private cloud browser sessions (beta, invite-only). All 40 tools share the one VIRTUALSMS_API_KEY.

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?

Run a blog, tool list, or Telegram channel? Earn up to 15% lifetime commission.

Become an affiliate