Integration

WinSMS integration

WinSMS is a South African bulk SMS service. Send one SMS text to up to 1000 recipients, or several different texts in one call, immediately or scheduled (South African time); check the delivery status of sent messages; list and cancel scheduled messages, which refunds their credits; read incoming replies, opt-out messages and short or long code messages; check the credit balance; list sub accounts and move credits between the main account and its sub accounts. This REST API has no webhook routes: read replies with list_incoming_sms and delivery results with get_sms_statuses. Authentication is a WinSMS API key, sent as is in the Authorization header.

Connect WinSMS How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in WinSMS.Built from the 11 WinSMS tools below, on the connection you add once.

What you can do with WinSMS

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Incoming, 2 operations

list_incoming_smsList incoming smsGETLists the SMS replies received by the account, paged with offset and limit (100 by default, at most 1000). Each one carries the sender's number, the text, when it arrived and the apiMessageId of the last message sent to that number.
list_shortcode_messagesList shortcode messagesGETLists the messages received on the account's WinSMS short or long code, paged with offset and limit (100 by default, at most 1000). Only available to accounts that have a WinSMS short or long code.

Balance, 1 operation

get_credit_balanceGet credit balanceGETReturns the account's remaining WinSMS credit balance, a number with one decimal place.

Delete, 1 operation

delete_scheduled_smsDelete scheduled smsPOSTCancels scheduled SMS messages that have not been sent yet, from up to 1000 apiMessageId values, and refunds their credits. Each result says whether that message was deleted, and the credits refunded.

Optout, 1 operation

list_optout_messagesList optout messagesGETLists the opt-out SMS messages the account has received, together with the numbers added to its opt-out list by hand.

Scheduled, 1 operation

list_scheduled_smsList scheduled smsGETLists the scheduled SMS messages that have not been sent yet, paged with offset and limit (100 by default, at most 1000), with when each was submitted, when it will be sent and the credits it will refund if cancelled.

Send, 1 operation

send_smsSend smsPOSTSends one SMS text to 1 to 1000 recipients, immediately or at a scheduled time. Each accepted recipient gets an apiMessageId, which get_sms_statuses and delete_scheduled_sms take; a declined one says why in acceptError.

Sendmulti, 1 operation

send_sms_batchSend sms batchPOSTSends several different SMS texts in one call, each to its own recipients and with its own optional schedule and segment limit; at most 1000 recipients across all messages.

Statu, 1 operation

get_sms_statusesGet sms statusesPOSTReturns the delivery status of messages already sent, from up to 1000 apiMessageId values returned by send_sms or send_sms_batch: whether each was delivered, its status code when not, the time of its last update and its credit cost.

Subaccount, 1 operation

list_subaccountsList subaccountsGETLists the sub accounts owned by the main account, with each one's account number (as transfer_credits takes it), the name of its user and its credit balance.

Transfer, 1 operation

transfer_creditsTransfer creditsPOSTMoves credits from the main account to a sub account, from a sub account to the main account, or between two sub accounts.

Use WinSMS from Claude Code, Cursor or Codex

Connect WinSMS in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its WinSMS operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect WinSMS

Create your workspace
Sign up free. Nothing to install.
Connect WinSMS once
Add your WinSMS connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.