Integration

Conversive integration

Conversive (formerly SMS-Magic) is a business text messaging platform. With this integration an agent can check that an API key is valid, send one SMS or MMS, send a batch of SMS in one call, and read the delivery status of messages sent in the last 24 hours, by the message id returned at send time or by the numeric SMS id. Delivery reports and incoming SMS are pushed by Conversive to a URL registered with the account, not fetched through this API. Not exposed: the v2.0 API (send messages, credit balance), which takes the API key inside the JSON body, and the Voice API, which runs on another host with a bearer token whose issuance is not documented. Authentication is the account's API key, sent in the apiKey header; api_host is the API host of the account's data center: api.beconversive.com (US), eu-api.beconversive.com (EU) or aus-api.beconversive.com (Australia).

Connect Conversive How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Conversive

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.

Sms status, 2 operations

get_sms_statusGet sms statusPOSTGet the delivery status of SMS sent in the last 24 hours, by the ids (UUIDs) send_sms or send_bulk_sms returned. Read only. Returns one entry per SMS: sms_id, status, delivered_on.
get_sms_status_by_numeric_idGet sms status by numeric idPOSTGet the delivery status of SMS sent in the last 24 hours, by numeric SMS ids (123) instead of the UUIDs send_sms returns; for those use get_sms_status. Read only. Returns sms_id, status, delivered_on per SMS.

Api key, 1 operation

validate_api_keyValidate api keyGETCheck whether the account's API key is accepted. Read status: success means valid. An invalid key has been seen answering HTTP 200 with status Error, so test the status value, not the HTTP code.

Bulk, 1 operation

send_bulk_smsSend bulk smsPOSTSend several SMS in one call, each with its own number, text and sender id. Billed and sent at once. An entry is sent only if its status is submitted with an id: a failure can answer HTTP 200 with status Error.

Send, 1 operation

send_smsSend smsPOSTSend one SMS (or MMS, with mms_url_list) to one mobile number. Billed and sent at once. Sent only if status is submitted with an id for get_sms_status: a failure can answer HTTP 200 with status Error.

Use Conversive from Claude Code, Cursor or Codex

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

Create your workspace
Sign up free. Nothing to install.
Connect Conversive once
Add your Conversive 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.