Integration

Quriiri integration

Quriiri is a Finnish business messaging service for SMS and RCS. Send an SMS to one or more numbers (alphanumeric, national or international sender, message templates, flash SMS, scheduling, validity and delivery report URL), cancel a scheduled SMS, read the delivery status of sent messages by time range or by DR id, list the sender ids authorized or registered for the account, and send RCS messages with an optional SMS fallback. Receiving messages (push callbacks or the pull API), the contacts and groups API (served from the user interface host), sender id authorization requests (a multipart form), the Verify, NPS survey and SMS survey application APIs, the deprecated Dialog API, SMPP and SMTP are not exposed. Connecting needs two values from the Quriiri web UI: the HTTP common API URL from Message Router > Resources, entered as a full https:// origin, and an API key created under Management > API keys, sent as Authorization: Bearer <key>. RCS also needs an RCS agent that Quriiri support configures for the account. Since 4 May 2026 every sender id must be registered with Traficom or authorized in the service.

Connect Quriiri How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Quriiri

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, 2 operations

cancel_scheduled_smsCancel scheduled smsDELETECancels an SMS that was scheduled with send_sms (scheduletime) and has not been sent yet, identified by its messageid.
send_smsSend smsPOSTSends an SMS to one or more numbers (set scheduletime to schedule it) and returns per destination the converted international number, status (CREATED or FAILED), failure reason and the messageid (DR id) for get_sms_status or cancel_scheduled_sms.

Sms status, 2 operations

get_sms_statusGet sms statusGETReturns the status of one SMS by its DR id (the messageid returned by send_sms): direction, status, failure reason, status time, batch id, billing reference, country code and body parts.
list_sms_statusesList sms statusesGETLists the status of the account's SMS messages within a time range (DR id, direction, status, failure reason, batch id, billing reference, country code, body parts), optionally only those with one status.

Rcs message, 1 operation

send_rcs_messageSend rcs messagePOSTSends an RCS message to one or more numbers through an RCS route, optionally with suggested replies or actions and an SMS fallback, and returns per destination the converted number, status, failure reason and message id.

Sender id, 1 operation

list_sender_idsList sender idsGETLists the sender ids the account may use: those authorized in the service and those registered with Traficom.

Use Quriiri from Claude Code, Cursor or Codex

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

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