# How to connect WaniKani to Hermes Agent (paste one key, 16 tools) > Connect WaniKani to Hermes with ClawLink: paste your WaniKani key once and 16 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/wanikani Most guides for giving Hermes Agent WaniKani 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 WaniKani setup: pair once in the browser and your always-on Hermes agent can act on WaniKani 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 WaniKani. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect WaniKani** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Paste this into Hermes to set up ClawLink:** > 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 with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 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. **Alternative for any agent (no plugin needed):** if the Hermes Agent 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 wanikani # connect WaniKani (browser OAuth) npx -y @useclawlink/cli actions wanikani # list available actions npx -y @useclawlink/cli run wanikani --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above walks Hermes through this. By hand, it is four commands and a browser approval: ```bash 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 test ``` Then connect WaniKani in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your WaniKani API key once. Verify the connection by asking Hermes: > Pull the relevant data from WaniKani, 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once WaniKani is connected in the dashboard, that agent calls the same 16 WaniKani 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). ## WaniKani MCP for Hermes Looking for a WaniKani MCP server for Hermes Agent? ClawLink connects WaniKani to Hermes Agent and exposes 16 WaniKani 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 OpenClaw instead? The [OpenClaw WaniKani integration](https://claw-link.dev/openclaw/wanikani) works the same way. ## What the Hermes Agent WaniKani integration can do 16 WaniKani tools are ready for Hermes Agent once the account is connected. ### All 16 WaniKani tools for Hermes | Tool | What it does | |---|---| | **Get assignments** `wanikani_get_assignments` | Retrieve one assignment by ID, or list the connected user's assignments using progress | | **Get level progressions** `wanikani_get_level_progressions` | Retrieve one level-progression record by ID, or list the user's level history with ID and | | **Get resets** `wanikani_get_resets` | Retrieve one account-reset record by ID, or list account level-reset history | | **Get review statistics** `wanikani_get_review_statistics` | Retrieve one per-subject review statistic by ID, or list answer totals, streaks, and accuracy | | **Get reviews** `wanikani_get_reviews` | Retrieve one completed review by ID, or list completed reviews filtered by review IDs, subject | | **Get spaced repetition systems** `wanikani_get_spaced_repetition_systems` | Retrieve one spaced-repetition system by ID, or list SRS definitions and their stage intervals | | **Get study materials** `wanikani_get_study_materials` | Retrieve one study-material record by ID, or list the user's subject notes and meaning synonyms | | **Get study summary** `wanikani_get_study_summary` | Get lessons available now and review availability over the next 24 hours for the connected user | | **Get subjects** `wanikani_get_subjects` | Retrieve one WaniKani subject by ID, or search radicals, kanji, vocabulary, and kana vocabulary | | **Get user** `wanikani_get_user` | Get the connected user's identity, level, subscription status, vacation state, and application | | **Get voice actors** `wanikani_get_voice_actors` | Retrieve one WaniKani pronunciation voice actor by ID, or list voice actors with ID and | | **Create study material** `wanikani_create_study_material` | Create the sole study-material record for a subject, optionally with notes or meaning synonyms | | **Update study material** `wanikani_update_study_material` | Update at least one note or meaning-synonym field on an existing study-material record without | | **Update user preferences** `wanikani_update_user_preferences` | Update one or more supported WaniKani lesson or review preferences | | **Start assignment** `wanikani_start_assignment` | Irreversibly mark one unlocked lesson assignment as started and move it into reviews | | **Submit review** `wanikani_submit_review` | Irreversibly submit a completed review, changing assignment progress and review statistics | ## Example prompts **Get Assignments** > Pull the relevant data from WaniKani, summarize it in plain English, and point out anything that needs attention. **Get Level Progressions** > Pull the relevant data from WaniKani, summarize it in plain English, and point out anything that needs attention. **Get Resets** > Pull the relevant data from WaniKani, summarize it in plain English, and point out anything that needs attention. **Get Review Statistics** > Pull the relevant data from WaniKani, summarize it in plain English, and point out anything that needs attention. ## 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 WaniKani working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the WaniKani API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected WaniKani 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 WaniKani. | 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 WaniKani actions to the runtime in a format your agent can reliably use. | 16 tools for WaniKani are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes WaniKani 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 WaniKani in the browser, and the 16 tools above work from chat. There is no SDK and no config file, and the WaniKani 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. ### Hermes paired but still can't use WaniKani 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 WaniKani 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 WaniKani tools WaniKani 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 WaniKani 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. ### WaniKani 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 WaniKani has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a Hermes Agent WaniKani integration? Yes. ClawLink is the fastest way to connect Hermes to WaniKani: link your WaniKani account once in the browser and Hermes Agent can call the WaniKani API through 16 ready-made tools — no custom code or token handling. ### How do I connect WaniKani 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 WaniKani in the dashboard and Hermes can use it from the next message — no config files, and the WaniKani key you paste is stored server-side instead of in your environment. ### How long does it take to connect WaniKani to Hermes Agent? About two minutes. Sign in, click Connect next to WaniKani in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring WaniKani 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 WaniKani working from chat. ### Hermes paired but still can't use WaniKani 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`. ## Related - [Hermes GitHub integration](https://claw-link.dev/hermes/github) — Manage repositories, issues, pull requests, and workflows - [Hermes PagerDuty integration](https://claw-link.dev/hermes/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture](https://claw-link.dev/hermes/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.