Integration

Arpoone integration

Arpoone (by Sendit) sends transactional SMS, email and RCS messages and manages a marketing audience. Send one SMS, email or RCS message per call (billed from the organisation's balance), read the Email and SMS balance, create short links, and add, edit or replace audience contacts. Senders, email domains, audiences and RCS templates are set up in the Arpoone platform first. Balance transfers between organisations, SMS sender registration requests and per-message delivery webhooks are not exposed. Arpoone's terms forbid unsolicited marketing without the recipient's prior consent. Authentication is a user API key (User Settings, API Key) sent as Authorization: Bearer; most tools also need the Organization ID from the dashboard.

Connect Arpoone How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Arpoone

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.

Recipient, 4 operations

add_recipientAdd recipientPOSTAdd a contact (recipient) to the organisation's audience for real; the audience must exist in Arpoone and the plan's contact limit applies. Add only people who gave prior consent to be contacted. Fails if the key fields match an existing contact.
replace_recipientReplace recipientPUTReplace an audience contact completely, for real: found by the key fields in fields, every other field, tag and subscription is replaced; any left out is emptied. Subscribe only people with prior consent. Prefer update_recipient_by_key.
update_recipientUpdate recipientPATCHEdit an audience contact by its id (from add_recipient), for real. Sent fields are updated or added, sent tags added, sent subscriptions replace the current ones. Key fields cannot change. Subscribe only people with prior consent.
update_recipient_by_keyUpdate recipient by keyPATCHEdit an audience contact found by its key fields, for real. Sent fields are updated or added, sent tags added, sent subscriptions replace the current ones. Key fields cannot change. Subscribe only people with prior consent.

Balance, 1 operation

get_balanceGet balancePOSTRead the current Email and SMS balance of up to 50 organisations: email units left, and SMS left per destination country. Read-only. A per-organisation error still returns success: read balances[].error.

Email, 1 operation

send_emailSend emailPOSTSend one transactional email for real to consenting people. Billed from the organisation's balance (cost in the result). from must use a domain verified in Arpoone. A refused message still returns success: read messages[0].status and error.

Rcs message, 1 operation

send_rcsSend rcsPOSTSend one RCS message for real to a consenting person, as text or from an Arpoone template, optional fallback SMS. Billed from the organisation's balance. A refused message still returns success: read messages[0].status and error.

Short url, 1 operation

create_short_urlsCreate short urlsPOSTCreate short links (arpn.me domain) for up to 100 URLs, for real; each redirects to its original URL. The feature must be enabled for the organisation by Arpoone support.

Sms, 1 operation

send_smsSend smsPOSTSend one SMS for real to a consenting person: to (number with country code), from (an approved sender), text. Billed from the organisation's balance. A refused message still returns success: read messages[0].status and error.

Use Arpoone from Claude Code, Cursor or Codex

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

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