MCP server for JoltSMS — provision real-SIM phone numbers and receive OTP codes
Connect Joltsms to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP server for JoltSMS — provision real-SIM phone numbers and receive OTP codes. The joltsms mcp server is what makes that connection.
MCP server for JoltSMS — provision dedicated real-SIM US phone numbers and receive SMS/OTP codes through AI agents.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
joltsms_list_numbers — List active numbers with service labels, tags, and unread countsjoltsms_get_number — Full details for a single numberjoltsms_update_number — Set service label, tags, or notes on a numberjoltsms_provision_number — Rent a new dedicated real-SIM US number ($50/mo)joltsms_release_number — Cancel/release a number at end of billing periodjoltsms_list_messages — List recent SMS with parsed OTP codesjoltsms_mark_read — Mark single or bulk messages as readjoltsms_wait_for_sms — Poll until an SMS arrives (key tool for OTP flows)joltsms_get_latest_otp — Get the most recent parsed verification codejoltsms_billing_status — Check all subscriptions with billing healthConfiguration is passed through the environment: JOLTSMS_API_KEY, JOLTSMS_API_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
This sits in the payments and commerce group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Joltsms's toolset — joltsms_list_numbers, joltsms_get_number, joltsms_update_number and 7 more — is a fair guide to whether it matches your workflow. It is maintained by rchanllc; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Joltsms's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| joltsms_list_numbers | List active numbers with service labels, tags, and unread counts |
| joltsms_get_number | Full details for a single number |
| joltsms_update_number | Set service label, tags, or notes on a number |
| joltsms_provision_number | Rent a new dedicated real-SIM US number ($50/mo) |
| joltsms_release_number | Cancel/release a number at end of billing period |
| joltsms_list_messages | List recent SMS with parsed OTP codes |
| joltsms_mark_read | Mark single or bulk messages as read |
| joltsms_wait_for_sms | Poll until an SMS arrives (key tool for OTP flows) |
| joltsms_get_latest_otp | Get the most recent parsed verification code |
| joltsms_billing_status | Check all subscriptions with billing health |
{
"mcpServers": {
"joltsms": {
"command": "npx",
"args": ["-y", "@joltsms/mcp-server"],
"env": {
"JOLTSMS_API_KEY": "jolt_sk_your_key_here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| JOLTSMS_API_KEY | Credential the server authenticates with. | Yes |
| JOLTSMS_API_URL | Endpoint or connection string the server talks to. | Yes |
Payments infrastructure meets AI — customers, invoices, subscriptions and current API docs from Stripe's server.
Build for Shopify with current APIs — the official Dev MCP server for schema-accurate storefront and admin code.
Give your AI assistant a supervised window into your Interactive Brokers account — balances, positions, live quotes and orders.
Invoices, payments and disputes through PayPal's official server — commerce operations by conversation.
Enables querying and listing Azure resources and costs directly from an MCP client.
Empowers LLMs with Bitcoin Lightning Network payment capabilities via the ZBD API.