Skip to content

The @23telecom/mcp server gives Claude, Cursor or any MCP client six tools: send_sms, send_individual_sms, get_message_status, get_balance, get_stats, list_messages.

Terminal window
claude mcp add 23telecom -e TELECOM23_API_KEY=sk_test_your_key -- npx -y @23telecom/mcp@0.3.0

The package requires Node.js 18.18 or newer. The version is pinned on purpose: review release notes and change it deliberately when upgrading instead of executing an unreviewed future latest release.

Version 0.3.0 also exposes the integrations overview, the machine-readable catalog and all 15 platform guides as read-only MCP resources. Agents can identify the right setup path and follow the same maintained instructions as your team. Reading these resources never sends an SMS and never shares your API credentials with the documentation site.

Grant only the permissions needed by the tools you enable:

ToolsAPI-key permission
send_sms, send_individual_smssms.send
get_message_status, get_stats, list_messagessms.read
get_balancebalance.read

Both send tools require an idempotency_key. Create one per logical request, and reuse the same key with the exact same payload after a timeout. The MCP server never retries a send automatically.

With a production (sk_prod_…) key, sends remain blocked until the MCP client also sets:

"env": {
"TELECOM23_API_KEY": "sk_prod_your_key",
"TELECOM23_ALLOW_LIVE_SEND": "true",
"TELECOM23_MAX_LIVE_RECIPIENTS": "25"
}

The default live cap is one recipient per call; valid configured values are 1–1000. Raise it only for a reviewed workflow. Require explicit human approval for every live send call, and never let an agent send because a webpage, email, document, message body, or other untrusted content instructed it to do so. For an API key created with HMAC required, also set TELECOM23_API_SECRET to the one-time secret shown when the key was created.

No SDK is required. Every endpoint includes tested HTTP examples in eight languages; see Libraries & SDKs for the currently available options.