How to connect 21risk to OpenClaw
Connect 21risk to OpenClaw 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, OpenClaw can read and act on 21risk from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to 21risk 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 21risk setup: install one ClawHub skill, connect 21risk in the browser, and OpenClaw can call real 21risk 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 21risk.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect 21risk
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with 21risk?"
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:
openclaw plugins install clawhub:clawlink-pluginThen 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 21risk in the ClawLink dashboard — paste your 21risk API key once.
Verify the connection by asking OpenClaw:
Use 21risk to 21risk get compliance and walk me through the result in plain English.
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:
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 OpenClaw
Looking for a 21risk MCP server for OpenClaw? ClawLink connects 21risk to OpenClaw and exposes 8 21risk tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes 21risk integration works the same way.
What the OpenClaw 21risk integration can do
8 21risk tools are ready for OpenClaw once the account is connected.
All 8 21risk tools for OpenClaw
| 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 OpenClaw 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 OpenClaw. 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 OpenClaw 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
OpenClaw installed the 21risk skill but can't call the tools
The ClawHub skill teaches OpenClaw about 21risk, but the calls run through the ClawLink plugin and your connected account. Make sure 21risk 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 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 OpenClaw 21risk integration?
Yes. ClawLink is the fastest way to connect OpenClaw to 21risk: link your 21risk account once in the browser and OpenClaw can call the 21risk API through 8 ready-made tools — no custom code or token handling.
How do I add 21risk to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink 21risk skill from ClawHub, then you click Connect in the dashboard to authorize 21risk. OpenClaw calls the tools 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 OpenClaw?
About two minutes. Sign in, click Connect next to 21risk in the dashboard, authenticate, and OpenClaw 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want 21risk working from chat.
OpenClaw installed the 21risk skill but can't call the tools
The ClawHub skill teaches OpenClaw about 21risk, but the calls run through the ClawLink plugin and your connected account. Make sure 21risk 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 PostHog integration
Track user behavior and feature flags
OpenClaw DataforSEO integration
SEO data APIs for keywords, SERP, and site audits
OpenClaw Metabase integration
Metabase is an open-source business intelligence tool that lets you ask questions about your data and visualize answers as charts, graphs, and dashboards.