How to connect lc.cx to OpenClaw
Connect lc.cx to OpenClaw with ClawLink: paste your lc.cx key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine.
lc.cxAPI KEYMCPlc.cx provides URL shortening, branded domains, workspaces, tags, click statistics, and QR code generation through its API.. Once connected, OpenClaw can read and act on lc.cx from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to lc.cx 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 lc.cx setup: install one ClawHub skill, connect lc.cx in the browser, and OpenClaw can call real lc.cx 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 lc.cx.
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 lc.cx
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with lc.cx?"
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 lc.cx in the ClawLink dashboard — paste your lc.cx API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from lc.cx, summarize it in plain English, and point out anything that needs attention.
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 lc.cx is connected in the dashboard, that agent calls the same 10 lc.cx tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
lc.cx MCP for OpenClaw
Looking for a lc.cx MCP server for OpenClaw? ClawLink connects lc.cx to OpenClaw and exposes 10 lc.cx tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes lc.cx integration works the same way.
What the OpenClaw lc.cx integration can do
10 lc.cx tools are ready for OpenClaw once the account is connected. The 8 below are the ones people reach for most; your agent can call all 10.
8 of 10 lc.cx tools for OpenClaw
| Tool | What it does |
|---|---|
Get account context lc_cx_get_account_context | Return lc.cx plan and short-link quota information together with available domains and |
Get short link lc_cx_get_short_link | Retrieve one short link by its lc.cx link id from the selected workspace |
List short links lc_cx_list_short_links | Return one page of recently created short links in the selected workspace, with an offset for |
List tags lc_cx_list_tags | Return all tags available in the selected workspace for organizing short links |
Create short link lc_cx_create_short_link | Shorten one destination URL on lc.cx, optionally choosing its path, tags, note, and workspace |
Create tags lc_cx_create_tags | Create one or more tags in a workspace and return their ids for attaching to short links |
Update short link lc_cx_update_short_link | Update a short link's destination, note, or complete tag assignment |
Update tag lc_cx_update_tag | Update the name or color of one tag in the selected workspace |
Try it: find the lc.cx tool you need
Browse the 8 lc.cx tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from lc.cx, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from lc.cx, summarize it in plain English, and point out anything that needs attention.
List the relevant items in lc.cx, group them by priority, and recommend what OpenClaw should do next.
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 lc.cx working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the lc.cx API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected lc.cx 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 lc.cx. | 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 lc.cx actions to the runtime in a format your agent can reliably use. | 10 tools for lc.cx are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes lc.cx 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 lc.cx in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the lc.cx 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 lc.cx skill but can't call the tools
The ClawHub skill teaches OpenClaw about lc.cx, but the calls run through the ClawLink plugin and your connected account. Make sure lc.cx 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 lc.cx 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 lc.cx tools
lc.cx 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 lc.cx 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.
lc.cx 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 lc.cx 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 lc.cx integration?
Yes. ClawLink is the fastest way to connect OpenClaw to lc.cx: link your lc.cx account once in the browser and OpenClaw can call the lc.cx API through 10 ready-made tools — no custom code or token handling.
How do I add lc.cx to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink lc.cx skill from ClawHub, then you click Connect in the dashboard to authorize lc.cx. OpenClaw calls the tools from the next message — no config files, and the lc.cx key you paste is stored server-side instead of in your environment.
How long does it take to connect lc.cx to OpenClaw?
About two minutes. Sign in, click Connect next to lc.cx in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring lc.cx 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 lc.cx working from chat.
OpenClaw installed the lc.cx skill but can't call the tools
The ClawHub skill teaches OpenClaw about lc.cx, but the calls run through the ClawLink plugin and your connected account. Make sure lc.cx 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
GitHub
Manage repositories, issues, pull requests, and workflows
PagerDuty
Manage incidents, on-call schedules, and services
SafetyCulture
SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.