# How to connect Hjarni to OpenClaw (paste one key, 15 tools) > Connect Hjarni to OpenClaw with ClawLink: paste your Hjarni key once and 15 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/hjarni The usual route to Hjarni 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 Hjarni setup: install one ClawHub skill, connect Hjarni in the browser, and OpenClaw can call real Hjarni 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 Hjarni. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Hjarni** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect hjarni # connect Hjarni (browser OAuth) npx -y @useclawlink/cli actions hjarni # list available actions npx -y @useclawlink/cli run hjarni --input '' # execute (add --confirm for writes) ``` ### 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: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then 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 Hjarni in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Hjarni API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Hjarni, 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: ```bash npx -y @useclawlink/cli login ``` `login` 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](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Hjarni MCP for OpenClaw Looking for a Hjarni MCP server for OpenClaw? ClawLink connects Hjarni to OpenClaw and exposes 15 Hjarni tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Hjarni integration](https://claw-link.dev/hermes/hjarni) works the same way. ## What the OpenClaw Hjarni integration can do 15 Hjarni tools are ready for OpenClaw 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 OpenClaw | 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 | ## Example prompts **Get Account Status** > Pull the relevant data from Hjarni, summarize it in plain English, and point out anything that needs attention. **Get Note** > Pull the relevant data from Hjarni, summarize it in plain English, and point out anything that needs attention. **List Containers** > List the relevant items in Hjarni, group them by priority, and recommend what OpenClaw should do next. **List Notes** > List the relevant items in Hjarni, 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 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 OpenClaw 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](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Hjarni skill but can't call the tools The ClawHub skill teaches OpenClaw about Hjarni, but the calls run through the ClawLink plugin and your connected account. Make sure Hjarni 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 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. ### Is there a OpenClaw Hjarni integration? Yes. ClawLink is the fastest way to connect OpenClaw to Hjarni: link your Hjarni account once in the browser and OpenClaw can call the Hjarni API through 15 ready-made tools — no custom code or token handling. ### How do I add Hjarni to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Hjarni skill from ClawHub, then you click Connect in the dashboard to authorize Hjarni. OpenClaw calls the tools 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 OpenClaw? About two minutes. Sign in, click Connect next to Hjarni in the dashboard, authenticate, and OpenClaw 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Hjarni working from chat. ### OpenClaw installed the Hjarni skill but can't call the tools The ClawHub skill teaches OpenClaw about Hjarni, but the calls run through the ClawLink plugin and your connected account. Make sure Hjarni 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 Trello integration](https://claw-link.dev/openclaw/trello) — Manage boards, lists, and cards - [Moco tools](https://claw-link.dev/openclaw/moco) — MOCO is a business management software offering project management, time tracking, and invoicing solutions. - [OpenClaw ClickUp integration](https://claw-link.dev/openclaw/clickup) — Manage tasks, docs, goals, and sprints