Integration

Kudosity integration

Kudosity (the former Burst SMS) TransmitMessage v2 API: send SMS, MMS (Australian numbers only), WhatsApp template or text messages and RCS messages (beta) one recipient per call, read back sent messages with their delivery status, check whether numbers can receive RCS, manage the account's event webhooks, and register and verify personal mobile numbers as senders. Every send is a real, billed message to a real handset at your account's rates; marketing messages must offer an opt-out and WhatsApp recipients must have opted in. Webhook updates are not exposed (the vendor resets every field left out, and webhook URLs are not returned), nor are multi-recipient sends, contact lists and keywords, which belong to the older TransmitSMS v1 API. The API allows 15 calls per second per account (HTTP 429 OVER_LIMIT beyond, and dropped requests are not retried). Authentication is the API key from the account SETTINGS page, API Settings section, sent in the x-api-key header.

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Kudosity

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.

Webhook, 4 operations

  • create_webhookCreate webhookPOSTCreates a real webhook: Kudosity then POSTs JSON events (SMS/MMS/WhatsApp/RCS status and inbound, link hits, opt-outs) to your https URL. Returns its id. Deliveries carry no signature to verify.
  • delete_webhookDelete webhookDELETEPermanently deletes a v2 webhook by its id (from list_webhooks). Returns message deleted.
  • get_webhookGet webhookGETReturns one v2 webhook by its id (from list_webhooks or create_webhook): name, event filter, rate limit and timestamps. The destination URL is not returned.
  • list_webhooksList webhooksGETLists the account's v2 webhooks with their name, event filter and rate limit. The destination URLs are not returned.

Rcs message, 3 operations

  • get_rcs_messageGet rcs messageGETReturns one RCS message by its id (from send_rcs_message or list_rcs_messages): content, status (QUEUED, SENT, DELIVERED, READ, FAILED) and event history.
  • list_rcs_messagesList rcs messagesGETLists the account's RCS messages, newest first, within a date window (default the last 365 days). Page with meta.pagination.next_cursor.
  • send_rcs_messageSend rcs messagePOSTBeta. Sends one real RCS message (text, or one image or video by public https URL) from your RCS agent to one recipient, billed at your account's rates. Returns data.id for get_rcs_message.

Sms, 3 operations

  • get_smsGet smsGETReturns one SMS sent or received through the v2 API by its id (from send_sms or list_sms): sender, recipient, text, delivery status, part count and timestamps.
  • list_smsList smsGETLists SMS sent or received through the v2 API, filtered by date, sender, recipient, message_ref, status, direction or country, with page and limit paging. Returns smses plus total_records.
  • send_smsSend smsPOSTSends one real SMS to one recipient, billed per message part (160 GSM characters for one part, 153 per part when split; 70 and 67 with emoji or non-Latin text). Returns the SMS id for get_sms.

Whatsapp message, 3 operations

  • get_whatsapp_messageGet whatsapp messageGETReturns one WhatsApp message by its id (from send_whatsapp_message or list_whatsapp_messages): content, status (QUEUED, SENT, DELIVERED, READ, FAILED) and its event history.
  • list_whatsapp_messagesList whatsapp messagesGETLists the account's WhatsApp messages, newest first, within a date window (default the last 365 days), optionally for one campaign. Page with meta.pagination.next_cursor.
  • send_whatsapp_messageSend whatsapp messagePOSTSends one real WhatsApp message (a pre-approved template, free text or a Meta Cloud API object) to one opted-in recipient, billed at your account's rates. Returns data.id for get_whatsapp_message.

Mms, 2 operations

  • get_mmsGet mmsGETReturns one MMS sent through the v2 API by its id (from send_mms): sender, recipient, subject, text, media URLs, status and timestamps.
  • send_mmsSend mmsPOSTSends one real MMS (text plus one media file of up to 400 KB) to one Australian number; billed as an MMS at your account's rates. Returns the MMS id for get_mms.

Sender registration, 2 operations

  • create_sender_registrationCreate sender registrationPOSTRegisters a personal mobile number as a sender (status PENDING_APPROVAL) and cancels any pending registration of that number. Next: request_sender_verification_code with data.registration_id.
  • list_sender_registrationsList sender registrationsGETLists sender registrations (personal mobile numbers and alphanumeric sender IDs) with their approval status, filterable by sender, status, registry status and account; page and limit paging.

Sender verification, 2 operations

  • confirm_sender_verification_codeConfirm sender verification codePOSTSubmits the code the registered number received; on success the verification becomes CONFIRMED and the registration VERIFIED. Failed attempts count against the limit of 5.
  • request_sender_verification_codeRequest sender verification codePOSTSends a real SMS verification code to a registered personal mobile number (from create_sender_registration). The code expires after 30 minutes; submit it with confirm_sender_verification_code.

Rcs capability, 1 operation

  • check_rcs_capabilityCheck rcs capabilityPOSTRead-only: checks which phone numbers can receive RCS from your RCS agent right now (code ENABLED, UNREACHABLE, ...), to choose between RCS and SMS before sending. Sends nothing.

Sender, 1 operation

  • delete_senderDelete senderDELETEPermanently deletes a sender phone number from your account (or from one of your child accounts with child_account_id). Returns no body.

Use Kudosity from Claude Code, Cursor or Codex

Connect Kudosity in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Kudosity 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 Kudosity

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Kudosity once

    Add your Kudosity connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. 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.

Kudosity integration FAQ

What can you do with the Kudosity integration?

LiveContext exposes 21 operations on Kudosity, covering webhook, rcs message, sms and whatsapp message.

Popular integrations

Browse the whole catalog