How to connect Hjarni to Hermes Agent
Connect Hjarni to Hermes with ClawLink: paste your Hjarni key once and 15 tools work from chat. No MCP server to run, nothing stored on your machine.
HjarniAPI KEYMCPHjarni is a personal knowledge management platform for organizing, searching, linking, and maintaining notes, containers, and tags.. Once connected, Hermes Agent can read and act on Hjarni from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Hjarni 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 Hjarni setup: pair once in the browser and your always-on Hermes agent can act on Hjarni for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect Hermes to Hjarni.
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 Hjarni
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Hjarni?"
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 Hjarni in the ClawLink dashboard — paste your Hjarni API key once.
Verify the connection by asking Hermes:
Pull the relevant data from Hjarni, 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 Hjarni is connected in the dashboard, that agent calls the same 15 Hjarni tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Hjarni MCP for Hermes
Looking for a Hjarni MCP server for Hermes Agent? ClawLink connects Hjarni to Hermes Agent and exposes 15 Hjarni tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Hjarni integration works the same way.
What the Hermes Agent Hjarni integration can do
15 Hjarni tools are ready for Hermes Agent once the account is connected. The 14 below are the ones people reach for most; your agent can call all 15.
14 of 15 Hjarni tools for Hermes
| Tool | What it does |
|---|---|
Get account status hjarni_get_account_status | Return the connected Hjarni identity, token scope, plan, teams, and current resource usage and |
Get note hjarni_get_note | Get one Hjarni note by ID with its Markdown body, tags, container, attachments, links, and |
List containers hjarni_list_containers | List Hjarni containers as active roots, archived roots, or all active containers in a flat view |
List notes hjarni_list_notes | List and filter personal Hjarni notes, including active, inbox, archived, or favorited notes |
List tags hjarni_list_tags | List all Hjarni tags and their note counts |
List trashed notes hjarni_list_trashed_notes | List recoverable trashed Hjarni notes with their deletion and scheduled purge times |
Create container hjarni_create_container | Create a root or nested Hjarni container for organizing notes |
Create note hjarni_create_note | Create a Markdown note in the inbox or a container |
Create notes hjarni_create_notes | Create 1-25 Markdown notes in order and return one result per input |
Create tag hjarni_create_tag | Create a Hjarni tag for organizing notes |
Rename tag hjarni_rename_tag | Rename an existing Hjarni tag without changing its note associations |
Restore note hjarni_restore_note | Restore a note from Trash before its scheduled purge and return the active note |
Update container hjarni_update_container | Update a Hjarni container's name, description, parent, position, or container-specific AI |
Update note hjarni_update_note | Update note metadata, placement, tags, or body |
Try it: find the Hjarni tool you need
Browse the 14 Hjarni 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 Hjarni, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Hjarni, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Hjarni, group them by priority, and recommend what Hermes should do next.
List the relevant items in Hjarni, group them by priority, and recommend what Hermes 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Hjarni working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Hjarni API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Hjarni 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 Hjarni. | 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 Hjarni actions to the runtime in a format your agent can reliably use. | 15 tools for Hjarni are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Hjarni 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 Hjarni in the browser, and the 15 tools above work from chat. There is no SDK and no config file, and the Hjarni 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
Hermes paired but still can't use Hjarni
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 Hjarni 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 Hjarni tools
Hjarni 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 Hjarni 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.
Hjarni 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 Hjarni has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a Hermes Agent Hjarni integration?
Yes. ClawLink is the fastest way to connect Hermes to Hjarni: link your Hjarni account once in the browser and Hermes Agent can call the Hjarni API through 15 ready-made tools — no custom code or token handling.
How do I connect Hjarni 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 Hjarni in the dashboard and Hermes can use it from the next message — no config files, and the Hjarni key you paste is stored server-side instead of in your environment.
How long does it take to connect Hjarni to Hermes Agent?
About two minutes. Sign in, click Connect next to Hjarni in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Hjarni up myself?
The alternative to ClawLink is usually manual API key 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 Hjarni working from chat.
Hermes paired but still can't use Hjarni
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.
