How to connect Linkhut to Hermes Agent
Connect Linkhut to Hermes 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, Hermes Agent can read and act on Linkhut from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Linkhut access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Linkhut setup: pair once in the browser and your always-on Hermes agent can act on Linkhut for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into Hermes to install the plugin and pair your account.
Set up ClawLink for Hermes and tell me when it's ready.
1. Install the plugin:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
2. Start pairing. It prints an approval link, so show me the link and stop, don't wait:
hermes clawlink begin
3. I'll approve it in my browser, then reply "approved".
4. When I say approved, finish setup:
hermes clawlink finish
5. Then run `hermes clawlink test` and tell me whether ClawLink is ready.Setup
It takes three steps to connect Hermes to Linkhut.
1Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable- 2
Connect Linkhut
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Linkhut?"
Install by command
The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin # prints an approval link — open it and approve
hermes clawlink finish # after approving in the browser
hermes clawlink testThen connect Linkhut in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking Hermes:
Pull the relevant data from Linkhut, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The Hermes 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 Hermes
Looking for a Linkhut MCP server for Hermes Agent? ClawLink connects Linkhut to Hermes Agent and exposes 5 Linkhut tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Linkhut integration works the same way.
What the Hermes Agent Linkhut integration can do
5 Linkhut tools are ready for Hermes Agent 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 Hermes
| 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 Hermes 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 Hermes Agent. 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 Hermes Agent 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
Hermes paired but still can't use Linkhut
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
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 Hermes Agent Linkhut integration?
Yes. ClawLink is the fastest way to connect Hermes to Linkhut: link your Linkhut account once in the browser and Hermes Agent can call the Linkhut API through 5 ready-made tools — no custom code or token handling.
How do I connect Linkhut to Hermes with ClawLink?
Install the plugin with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pair once: run hermes clawlink begin, approve the link in your browser, and run hermes clawlink finish. Connect Linkhut in the dashboard and Hermes can use it from the next message — no config files or API keys to manage.
How long does it take to connect Linkhut to Hermes Agent?
About two minutes. Sign in, click Connect next to Linkhut in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Linkhut working from chat.
Hermes paired but still can't use Linkhut
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
