Shop MCP

Connect a module

touchSMS

ShopMCP connects touchSMS SMS/MMS sending, credit previews, sender IDs, contacts, opt-outs, inbound replies, and OTP verification to Claude, ChatGPT, Cursor, and other MCP clients.

Live sends are write-gated

Operators can send SMS/MMS through touchSMS when writes are enabled for the workspace and the exact payload is confirmed. Use dry-run previews before bulk sends so credits, recipients, duplicates, opt-outs, sender IDs, and message parts can be reviewed.

1. Create an API key in touchSMS

In touchSMS, open Settings - API Settings, create a new API key for ShopMCP, then copy the generated Token ID and Token Secret.

touchSMS uses HTTP Basic Authentication. ShopMCP stores the token pair encrypted and sends API requests from the server, not from the browser.

2. Connect touchSMS in ShopMCP

Open Settings - Integrations, choose touchSMS, then paste the Token ID and Token Secret. ShopMCP verifies the connection by reading account details and sender IDs.

  • Account details confirm the credential pair is valid and show available credits.
  • Sender IDs confirm which dedicated, own-number, custom, or shared senders can be used.
  • A label is useful if an agency manages multiple touchSMS accounts.

3. Send with a preview first

ShopMCP can send live SMS/MMS through touchSMS when writes are enabled. For bulk or customer-facing sends, ask ShopMCP to preview the message first. The dry-run endpoint checks sender validity, recipient parsing, duplicates, opt-out-list rejection, Unicode, message parts, and credit usage before the live send.

Live sends are customer-facing

Write tools can send SMS/MMS messages, alter opt-outs, and start OTP verifications. Review the exact payload, sender ID, recipients, and schedule before confirming the action.

4. What you can ask

Common touchSMS questions
GoalExample promptWhat ShopMCP reads or does
Send a confirmed batchSend this order-delay SMS to these 42 customers after previewing cost and opt-out blocks.Dry-run first, then live send if writes are enabled and confirmed.
Preview a campaignDry-run this SMS batch and tell me the credit cost, invalid recipients, and opt-out blocks.touchSMS /sms/dry validation response.
Check readinessIs this touchSMS account ready to send customer notifications?Account credits, duplicate settings, timezone, sender IDs.
Review repliesShow inbound replies since yesterday and flag opt-outs or unhappy customers.Inbound polling by created_after or id_after.
Run OTPStart an OTP verification for this mobile and check the submitted code.Verification create/check/cancel endpoints.

5. Opt-outs and inbound replies

ShopMCP exposes touchSMS opt-out records and opt-out lists so agents can check whether a send should be blocked before it reaches the live endpoint. Inbound replies are available through polling with created_after or id_after.

Webhook gap

touchSMS recommends webhooks for realtime inbound messages, but the public Postman collection we implemented from does not include enough webhook setup and signature detail for a safe first version. The v1 integration uses documented polling and records the webhook gap.

6. Official references