Integration

SzybkiSMS integration

SzybkiSMS.pl (formerly GSMService.pl) is a Polish SMS and MMS gateway. Send SMS (PRO, ECO or 2WAY) and MMS messages to one or many recipients, now or at a scheduled time, check their price before sending, read the history and delivery status of sent messages, cancel scheduled ones, read and remove received messages, register sender names and pick the default one, and read the account balance. The sandbox host and the legacy SOAP and HTTP APIs are not exposed. Authentication is the REST API Access Token created in the SzybkiSMS user panel (API section), sent as a Bearer token.

Connect SzybkiSMS How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with SzybkiSMS

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.

Sender, 4 operations

add_senderAdd senderPOSTRequests a new sender name (2 to 11 characters). It is registered by operators and stays Pending until approved, so describe its use precisely in description.
delete_senderDelete senderDELETEDeletes a sender name from the account immediately. Pass the full name as returned by list_senders. Returns no body (HTTP 204).
list_sendersList sendersGETLists the sender names defined on the account with their status: only Active names can be used to send; Pending ones await operator registration. is_default marks the default sender.
set_default_senderSet default senderPATCHMakes one of the account's sender names the default, used when send_sms gets no sender. Pass the full name as returned by list_senders. Returns no body (HTTP 204).

Incoming, 3 operations

get_incoming_messagesGet incoming messagesGETReturns one or more received messages by id (comma-separated, at most 50), as returned by list_incoming_messages.
list_incoming_messagesList incoming messagesGETLists received SMS messages, newest first, one page at a time (page and limit, at most 50 per page). Each item has id, sender, recipient, date and message text.
remove_incoming_messagesRemove incoming messagesDELETERemoves received messages from the inbox by id (comma-separated, at most 50). Returns one item per id with status 204 when removed, or another status and an error object.

Message, 3 operations

cancel_messagesCancel messagesDELETECancels messages scheduled for later sending, by id (comma-separated, at most 50). Returns one item per id with status 204 when cancelled, or another status and an error object.
get_messagesGet messagesGETReturns the details and current status (status_code, status_description) of one or more sent messages by id (comma-separated, at most 50), as returned by send_sms or send_mms.
list_messagesList messagesGETLists sent messages with their current status, newest first, one page at a time (page and limit, at most 50 per page).

Account, 2 operations

get_account_detailsGet account detailsGETReturns the account login, type, balance (credit, in the account currency), limit, currency and whether it is the main account.
get_subaccount_detailsGet subaccount detailsGETReturns the details of one subaccount (an additional user of your account): login, balance, subcredit balance (null when unlimited), limit and currency.

Price, 2 operations

get_mms_priceGet mms pricePOSTCalculates the price of an MMS without sending it, one item per recipient (at most 50). Each item has price (PLN), and error is null when pricing succeeded.
get_sms_priceGet sms pricePOSTCalculates the price of an SMS without sending it, one item per recipient (at most 100). Each item has price (PLN) and parts, and error is null when pricing succeeded.

Mms, 1 operation

send_mmsSend mmsPOSTSends one MMS (billed) to one or more recipients (at most 50), immediately unless date is set. Returns one item per recipient: check status_code (QUEUED or REJECTED) and status_description.

Ping, 1 operation

pingPingGETChecks that the API is available (status OK or ERR) and returns its version and whether the host is the sandbox. Needs no token.

Sms, 1 operation

send_smsSend smsPOSTSends one SMS (billed) to one or more recipients (at most 100), immediately unless date is set. Returns one item per recipient: check status_code (QUEUED or REJECTED) and status_description.

Use SzybkiSMS from Claude Code, Cursor or Codex

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

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