Voidmob MCP

VoidMob MCP

Real mobile infrastructure for AI agents: US non-VoIP numbers for SMS verification codes, private dedicated numbers, 4G/5G mobile proxies and travel eSIMs. 28 tools, paid from a prepaid USD balance, with permission levels and optional spending limits that VoidMob enforces on every purchase.

Contents: Quick start · What your agent can do · Connect with one URL · Run locally · How money works · Owner controls · Tools · Agent skill · Configuration

Quick start

Fund the balance with crypto at dashboard.voidmob.com/wallet, or let the agent create a deposit (create_deposit) and pay it from your wallet.

What your agent can do

The agent quotes every purchase and asks before buying, unless you turned on buy without asking within a daily limit.

Connect with one URL

https://mcp.voidmob.com/mcp

Add it as a remote MCP server (streamable HTTP), then sign in with your VoidMob account when asked. Nothing to install and no API key to paste.

Menu names change between app versions: look for "custom connector" or "remote MCP server". Step-by-step guides: voidmob.com/mcp and voidmob.com/integrations. A client without sign-in support can send an API key instead: Authorization: Bearer vmk_live_....

What you choose when you connect

• Apps VoidMob does not recognize start at View. The agent only sees the tools its level allows.
• Optional spending limits: a maximum per order and a daily limit over a rolling 24 hours, net of refunds. Both are off by default. VoidMob enforces them on every purchase, so they hold whatever the app or agent does.
• Buy without asking: off by default and needs a daily limit. It only changes the server's instructions: the agent may buy without asking first, still quotes the price and reports every purchase. Your chat app's own approval prompts are a separate setting in that app.

Manage connected apps at dashboard.voidmob.com/account/connected-apps: change the level or limits, or disconnect.

• Up to 10 apps per account, and every new connection sends a security email.
• An app is disconnected after 90 days unused or when your login email changes.
• Apps can never turn auto-renew on, create IP-whitelist proxy lists or create webhook endpoints. Do those in the dashboard or with an API key.

Try it without an account

https://mcp.voidmob.com/sandbox/<any-random-id-of-16-or-more-letters-and-digits>

No sign-in, mock data, a $500 play balance, nothing charged. Make up your own id (16 or more letters, digits, - or _) and keep it private: that playground keeps its state. The bare https://mcp.voidmob.com/sandbox starts from fresh demo data on every call.

Run locally

1. Generate an API key at dashboard.voidmob.com/developers/api-keys (keys are 32-char secrets prefixed vmk_live_).
2. Add the server to your client (below), with the key as VOIDMOB_API_KEY.
3. Optional: set a permission level and spending limits on the key in the dashboard, and per-process limits with the owner controls.

No key yet? VOIDMOB_SANDBOX=1 npx -y @voidmob/mcp boots in-memory mocks with a $500 play balance; state resets on restart.

Claude Code

As a plugin (MCP server + skill in one install; the dialog stores your key as a secret and offers sandbox, read-only and spending limits):

/plugin marketplace add voidmobcom/voidmob-plugin

/plugin install voidmob@voidmob

Or the MCP server alone:

claude mcp add voidmob -s user -e VOIDMOB_API_KEY=vmk_live_... -- npx -y @voidmob/mcp

-s user makes the server available in every project; the key goes after -e and before --. The same plugin also installs in Codex and Gemini CLI: see voidmob-plugin.

Cursor

Add to ~/.cursor/mcp.json:

{

"mcpServers": { "voidmob": { "command": "npx", "args": ["-y", "@voidmob/mcp"], "env": { "VOIDMOB_API_KEY": "vmk_live_..." } } } }

Claude Desktop

One-click bundle. Download voidmob-mcp.mcpb from the latest GitHub release and open it (or drag it into Claude Desktop, or use Settings > Extensions > Advanced > Install Extension). Claude Desktop asks for the settings: API key (stored securely), sandbox mode, read-only, max per order, session budget and buy without asking (see Owner controls). Build it yourself with npm run pack:mcpb.

Or by config file. Open Settings > Developer > Edit Config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows) and add:

{

"mcpServers": { "voidmob": { "command": "npx", "args": ["-y", "@voidmob/mcp"], "env": { "VOIDMOB_API_KEY": "vmk_live_..." } } } }

VS Code

Add to .vscode/mcp.json (VS Code prompts for the key once and stores it securely):

{

"inputs": [ { "type": "promptString", "id": "voidmob-api-key", "description": "VoidMob API key (vmk_live_...)", "password": true } ], "servers": { "voidmob": { "type": "stdio", "command": "npx", "args": ["-y", "@voidmob/mcp"], "env": { "VOIDMOB_API_KEY": "${input:voidmob-api-key}" } } } }

Windsurf (Devin Desktop)

Open the MCP config from the Cascade panel menu (Open MCP config file). Current Devin Desktop builds keep it at ~/.config/devin/mcp_config.json (Windows: %APPDATA%\devin\mcp_config.json); Windsurf builds from before the rename use ~/.codeium/windsurf/mcp_config.json. Add:

{

"mcpServers": { "voidmob": { "command": "npx", "args": ["-y", "@voidmob/mcp"], "env": { "VOIDMOB_API_KEY": "vmk_live_..." } } } }

Codex CLI

codex mcp add voidmob --env VOIDMOB_API_KEY=vmk_live_... -- npx -y @voidmob/mcp

Or add to ~/.codex/config.toml (shared by the Codex CLI, the IDE extension and the ChatGPT desktop app):

[mcp_servers.voidmob]

command = "npx" args = ["-y", "@voidmob/mcp"] env = { VOIDMOB_API_KEY = "vmk_live_..." }

Gemini CLI

Add to ~/.gemini/settings.json, and export VOIDMOB_API_KEY in your shell (Gemini CLI hides variables named like a key from MCP servers unless the server's env lists them):

{

"mcpServers": { "voidmob": { "command": "npx", "args": ["-y", "@voidmob/mcp"], "env": { "VOIDMOB_API_KEY": "$VOIDMOB_API_KEY" } } } }

OpenClaw

Put VOIDMOB_API_KEY=vmk_live_... in ~/.openclaw/.env, then:

openclaw mcp set voidmob '{"command":"npx","args":["-y","@voidmob/mcp"],"env":{"VOIDMOB_API_KEY":"${VOIDMOB_API_KEY}"}}'

openclaw mcp doctor voidmob --probe

Or use the agent skill. Guide: voidmob.com/integrations/openclaw.

Hermes Agent

Put VOIDMOB_API_KEY=vmk_live_... in ~/.hermes/.env and add to ~/.hermes/config.yaml:

mcp_servers:

voidmob: command: "npx" args: ["-y", "@voidmob/mcp"] env: VOIDMOB_API_KEY: "${VOIDMOB_API_KEY}"

Or use the agent skill. Guide: voidmob.com/integrations/hermes-agent.

Pi

pi mcp add voidmob --env VOIDMOB_API_KEY='${VOIDMOB_API_KEY}' -- npx -y @voidmob/mcp

pi mcp list

The single quotes keep ${VOIDMOB_API_KEY} as a reference that Pi reads from your shell. Guide: voidmob.com/integrations/pi-coding-agent.

Grok Bot

1. In your Bot's Secrets, add a secret named VOIDMOB_API_KEY with your key as the value.
2. In chat, send: *Read https://voidmob.com/skill.md and follow it. My VoidMob API key is in the VOIDMOB_API_KEY secret.*

The skill runs the REST API with curl on the Bot's computer and reads the secret by name. A custom MCP server of the Command type running `npx -y @void