How to connect Saperly to OpenClaw
Connect Saperly to OpenClaw with ClawLink: paste your Saperly key once and 30 tools work from chat. No MCP server to run, nothing stored on your machine.


Saperly is the phone carrier for AI agents — phone numbers, voice, SMS, and compliance in one API.. Once connected, OpenClaw can read and act on Saperly from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Saperly access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Saperly setup: install one ClawHub skill, connect Saperly in the browser, and OpenClaw can call real Saperly actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to Saperly.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Saperly
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Saperly?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Saperly in the ClawLink dashboard — paste your Saperly API key once.
Verify the connection by asking OpenClaw:
Use Saperly to check consent and walk me through the result in plain English.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Saperly is connected in the dashboard, that agent calls the same 30 Saperly tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Saperly MCP for OpenClaw
Looking for a Saperly MCP server for OpenClaw? ClawLink connects Saperly to OpenClaw and exposes 30 Saperly tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Saperly integration works the same way.
What the OpenClaw Saperly integration can do
30 Saperly tools are ready for OpenClaw once the account is connected. The 29 below are the ones people reach for most; your agent can call all 30.
29 of 30 Saperly tools for OpenClaw
| Tool | What it does |
|---|---|
Check consent saperly_check_consent | Check whether a contact currently has active TCPA consent for one of your Saperly numbers |
Get call saperly_get_call | Fetch a single call by its id, returning its status, per-minute rate, final duration |
Get call recording saperly_get_call_recording | Get the audio recording for a call and return it as a downloadable file |
Get call transcript saperly_get_call_transcript | Fetch the transcript (conversation turns/segments) of a completed call by its id |
Get connection saperly_get_connection | Fetch a single connection (the AI answering brain / persona that handles calls and SMS) by its |
Get number saperly_get_number | Fetch a single phone number by its id, returning its E.164 phoneNumber, bound connectionId |
Get usage saperly_get_usage | Return the workspace usage summary and prepaid balance: calls {count, totalCostCents |
List calls saperly_list_calls | Return the full voice-call history (inbound + outbound) for the connected Saperly workspace |
List connections saperly_list_connections | Return every connection (the AI persona / answering 'brain' that handles calls and SMS) in the |
List consent saperly_list_consent | Return every TCPA consent record in the connected Saperly workspace, with each record's id |
List languages saperly_list_languages | Return the spoken languages Saperly supports for voice connections, each as a {code, name} pair |
List messages saperly_list_messages | Return SMS messages in the connected Saperly workspace (both inbound and outbound) |
List numbers saperly_list_numbers | Return every phone number provisioned in the connected Saperly workspace, with each number's |
List voices saperly_list_voices | List the text-to-speech voices available for Saperly connections |
Quote number price saperly_quote_number_price | READ-ONLY and FREE: quote the price to provision a phone number in a country/type, returning { |
Assign number connection saperly_assign_number_connection | Attach a connection (the AI persona / answering brain from SAPERLY_CREATE_CONNECTION) to a |
Create connection saperly_create_connection | Create a connection: the AI 'brain' that answers calls and (optionally) SMS on a Saperly phone |
End call saperly_end_call | End an in-progress call by its id, hanging up and settling the metered cost |
Place call saperly_place_call | PAID / METERED — places a REAL outbound voice call that RINGS A REAL PHONE and BILLS PER MINUTE |
Provision number saperly_provision_number | PAID / METERED: provision (buy) a new phone number in a country |
Record consent saperly_record_consent | Record TCPA consent for a contact so outbound SMS (SAPERLY_SEND_SMS) and calls |
Send sms saperly_send_sms | PAID / METERED: send a single SMS from one of your Saperly numbers to an E.164 destination |
Set number caller ID saperly_set_number_caller_id | Set the outbound caller ID name / CNAM (1-15 characters: letters, digits, spaces) presented to |
Set number sms sender saperly_set_number_sms_sender | Set the alphanumeric SMS sender id (1-11 alphanumeric chars, e.g |
Transfer call saperly_transfer_call | PAID / METERED — BLIND-transfers a LIVE, in-progress voice call to another destination to (an |
Update connection saperly_update_connection | Partially update a connection (the AI answering brain bound to a number) |
Release number saperly_release_number | PERMANENTLY AND IRREVERSIBLY release a phone number back to the carrier |
Revoke consent saperly_revoke_consent | Revoke a contact's TCPA consent for a given Saperly number, blocking further outbound contact |
Set number webhook saperly_set_number_webhook | Set the HTTPS webhook URL that Saperly POSTs this number's events (inbound SMS/calls, status) to |
Try it: find the Saperly tool you need
Browse the 29 Saperly tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Saperly to check consent and walk me through the result in plain English.
Pull the relevant data from Saperly, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Saperly, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Saperly, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Saperly working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Saperly API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Saperly account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Saperly. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Saperly actions to the runtime in a format your agent can reliably use. | 30 tools for Saperly are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Saperly to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Saperly in the browser, and the 30 tools above work from chat. There is no SDK and no config file, and the Saperly key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Saperly skill but can't call the tools
The ClawHub skill teaches OpenClaw about Saperly, but the calls run through the ClawLink plugin and your connected account. Make sure Saperly is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Saperly from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Saperly tools
Saperly tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Saperly call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Saperly returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Saperly has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Saperly integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Saperly: link your Saperly account once in the browser and OpenClaw can call the Saperly API through 30 ready-made tools — no custom code or token handling.
How do I add Saperly to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Saperly skill from ClawHub, then you click Connect in the dashboard to authorize Saperly. OpenClaw calls the tools from the next message — no config files, and the Saperly key you paste is stored server-side instead of in your environment.
How long does it take to connect Saperly to OpenClaw?
About two minutes. Sign in, click Connect next to Saperly in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Saperly up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Saperly working from chat.
OpenClaw installed the Saperly skill but can't call the tools
The ClawHub skill teaches OpenClaw about Saperly, but the calls run through the ClawLink plugin and your connected account. Make sure Saperly is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Related
OpenClaw DataRobot integration
DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets.
Chatbotkit tools
ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications.
Just One API tools
Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.