Integration

OtterText integration

OtterText is an SMS and MMS marketing platform for retail shops. Add or update customers (subscribers) matched by phone number, put them on lists and set their tags, opt them in or out of SMS and email, check their opt-in status, send or schedule an SMS or MMS, send one of the account's predefined templates, send an email, and register a webhook for form submissions and incoming messages. Sending SMS or MMS needs a 10DLC verified account; errors often arrive as HTTP 200 with status error, so check status on every reply. Authentication is the account's API token (requested in the OtterText dashboard under Settings, Keys), sent as a Bearer token.

Connect OtterText How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with OtterText

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.

Customer, 2 operations

add_customerAdd customerPOSTAdds a customer matched by phone; a new one is created and SENT an opt-in SMS. Optional list_id (from list_lists) and tags. Needs a 10DLC verified account, else HTTP 200 with status error, Action not allowed.
set_customer_optinSet customer optinPOSTOpts a customer, matched by phone, in or out of SMS and of email (sms and email: 1 = opt in, 0 = opt out). Changes what the customer receives. Check status: an error comes back as HTTP 200 with status error.

Message, 2 operations

schedule_messageSchedule messagePOSTSchedules an SMS or MMS to a customer for scheduled_date_time (it is then sent without further action). Set send_type to 2. Needs a 10DLC verified account, else HTTP 200 with status error and message Action not allowed.
send_messageSend messagePOSTSends an SMS or MMS to a customer now; a new number becomes a customer. Set send_type to 1. Needs a 10DLC verified account, else HTTP 200 with status error and message Action not allowed.

Email, 1 operation

send_emailSend emailPOSTSends an email (does not need 10DLC). The vendor documents this route by an example only: to, from, from_name, reply_to, subject, body, cc, bcc and attachment URLs. Check status in the reply.

List, 1 operation

list_listsList listsGETLists the customer lists of the account (id and title). Pass an id as list_id to add_customer or update_customer. Check status: an error comes back as HTTP 200 with status error.

Optinstatus, 1 operation

get_customer_optin_statusGet customer optin statusGETReturns the opt-in status of a customer matched by phone: customer.optincheck is 1 NewCustomer, 2 OptinRequested, 3 OptedIn, 4 OptedOut or 5 InvalidNumber. Check status, errors come back as HTTP 200.

Template, 1 operation

list_templatesList templatesPOSTLists the account's predefined message templates, a page at a time (start = offset, length = page size, draw = 1). Pass an id as template_id to send_template. Check status: an error comes back as HTTP 200 with status error.

Template message, 1 operation

send_templateSend templatePOSTSends one of the account's templates (template_id from list_templates) to a customer by SMS or MMS. send_type 1 sends now. Needs a 10DLC verified account, else HTTP 200 with status error and message Action not allowed.

Update, 1 operation

update_customerUpdate customerPOSTUpdates a customer matched by phone (never changes the phone). Omitted fields are kept; tags, when sent, replaces the whole tag set. Optional list_id from list_lists. Check status: errors come back as HTTP 200 with status error.

Webhook, 1 operation

set_webhookSet webhookPOSTAdds a webhook URL, or updates the one with the same URL, posted to on form submissions and/or incoming customer messages. The docs describe no signing secret for deliveries. Check status: errors come back as HTTP 200.

Use OtterText from Claude Code, Cursor or Codex

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

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