How to connect Linkhut to OpenClaw
Connect Linkhut to OpenClaw with ClawLink in one click — 5 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.
LinkhutOAUTH2MCPSave, organize, and share bookmarks and links. Once connected, OpenClaw can read and act on Linkhut from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Linkhut 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 Linkhut setup: install one ClawHub skill, connect Linkhut in the browser, and OpenClaw can call real Linkhut actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Linkhut skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Linkhut" (hith3sh/linkhut) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/linkhut
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Linkhut.
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 Linkhut
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Linkhut?"
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 Linkhut in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking OpenClaw:
Pull the relevant data from Linkhut, 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 Linkhut is connected in the dashboard, that agent calls the same 5 Linkhut tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Linkhut MCP for OpenClaw
Looking for a Linkhut MCP server for OpenClaw? ClawLink connects Linkhut to OpenClaw and exposes 5 Linkhut tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Linkhut integration works the same way.
What the OpenClaw Linkhut integration can do
5 Linkhut tools are ready for OpenClaw once the account is connected. The 4 below are the ones people reach for most; your agent can call all 5.
4 of 5 Linkhut tools for OpenClaw
| Tool | What it does |
|---|---|
Get all tags linkhut_get_all_tags | Retrieves a list of all tags and their usage counts for the authenticated user |
Get bookmarks linkhut_get_bookmarks | Retrieves bookmarks from the user's Linkhut account with optional filtering |
Add bookmark linkhut_add_bookmark | Adds a new bookmark to LinkHut |
Update bookmark linkhut_update_bookmark | Allows users to update an existing bookmark in LinkHut |
Try it: find the Linkhut tool you need
Browse the 4 Linkhut 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 Linkhut, summarize it in plain English, and point out anything that needs attention.
Use Linkhut to add bookmark and walk me through the result in plain English.
Update it in Linkhut, then show me exactly what changed.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual OAuth app 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 Linkhut working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Linkhut app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Linkhut through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Linkhut. | 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 Linkhut actions to the runtime in a format your agent can reliably use. | 5 tools for Linkhut are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Linkhut 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 Linkhut in the browser, and the 5 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Linkhut skill but can't call the tools
The ClawHub skill teaches OpenClaw about Linkhut, but the calls run through the ClawLink plugin and your connected account. Make sure Linkhut 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 Linkhut 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 Linkhut tools
Linkhut 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 Linkhut 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.
Linkhut 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.
OAuth finished in the browser but the account is still missing
Try reconnecting Linkhut and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.
FAQ
Is there a OpenClaw Linkhut integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Linkhut: link your Linkhut account once in the browser and OpenClaw can call the Linkhut API through 5 ready-made tools — no custom code or token handling.
How do I add Linkhut to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Linkhut skill from ClawHub, then you click Connect in the dashboard to authorize Linkhut. OpenClaw calls the tools from the next message — no config files or API keys to manage.
How long does it take to connect Linkhut to OpenClaw?
About two minutes. Sign in, click Connect next to Linkhut in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Linkhut up myself?
The alternative to ClawLink is usually manual OAuth app 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 Linkhut working from chat.
OpenClaw installed the Linkhut skill but can't call the tools
The ClawHub skill teaches OpenClaw about Linkhut, but the calls run through the ClawLink plugin and your connected account. Make sure Linkhut 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.
