How to connect 21risk to Hermes Agent
Connect 21risk to Hermes with ClawLink: paste your 21risk key once and 8 tools work from chat. No MCP server to run, nothing stored on your machine.
21riskAPI KEYMCP21RISK is a web application that simplifies working with checklists, audits, and actions, facilitating compliance and risk management processes.. Once connected, Hermes Agent can read and act on 21risk from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent 21risk 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 21risk setup: pair once in the browser and your always-on Hermes agent can act on 21risk 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 21risk.
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 21risk
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with 21risk?"
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 21risk in the ClawLink dashboard — paste your 21risk API key once.
Verify the connection by asking Hermes:
Use 21risk to 21risk get compliance and walk me through the result in plain English.
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 21risk is connected in the dashboard, that agent calls the same 8 21risk tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
21risk MCP for Hermes
Looking for a 21risk MCP server for Hermes Agent? ClawLink connects 21risk to Hermes Agent and exposes 8 21risk tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw 21risk integration works the same way.
What the Hermes Agent 21risk integration can do
8 21risk tools are ready for Hermes Agent once the account is connected.
All 8 21risk tools for Hermes
| Tool | What it does |
|---|---|
21risk get compliance _21risk_get_compliance | Retrieve compliance data for sites, categories, or questions |
21risk get items _21risk_get_items | Retrieve items (BETA) from the 21RISK OData API |
21risk get items per month _21risk_get_items_per_month | Retrieve fact table data for ItemsPerMonth, one row per question per site per month |
21risk get organizations _21risk_get_organizations | Retrieve organizations from the 21RISK OData API |
21risk get properties _21risk_get_properties | Fetch a list of properties related to sites, including COPE information and other relevant data |
21risk get reports _21risk_get_reports | Retrieve audit reports, including draft, published, and scheduled reports |
21risk get risk models _21risk_get_risk_models | Retrieve risk models used for audits and compliance |
21risk get riskmodel categories _21risk_get_riskmodel_categories | Retrieve risk model categories for grouping questions and compliance checks |
Try it: find the 21risk tool you need
Browse the 8 21risk tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Use 21risk to 21risk get compliance and walk me through the result in plain English.
Use 21risk to 21risk get items and walk me through the result in plain English.
Use 21risk to 21risk get items per month and walk me through the result in plain English.
Use 21risk to 21risk get organizations and walk me through the result in plain English.
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 21risk working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the 21risk API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected 21risk 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 21risk. | 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 21risk actions to the runtime in a format your agent can reliably use. | 8 tools for 21risk are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes 21risk 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 21risk in the browser, and the 8 tools above work from chat. There is no SDK and no config file, and the 21risk 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 21risk
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 21risk 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 21risk tools
21risk 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 21risk 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.
21risk 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 21risk 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 21risk integration?
Yes. ClawLink is the fastest way to connect Hermes to 21risk: link your 21risk account once in the browser and Hermes Agent can call the 21risk API through 8 ready-made tools — no custom code or token handling.
How do I connect 21risk 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 21risk in the dashboard and Hermes can use it from the next message — no config files, and the 21risk key you paste is stored server-side instead of in your environment.
How long does it take to connect 21risk to Hermes Agent?
About two minutes. Sign in, click Connect next to 21risk in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring 21risk 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 21risk working from chat.
Hermes paired but still can't use 21risk
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.
