# How to connect Rkvst to OpenClaw (paste one key, 24 tools) > Connect Rkvst to OpenClaw with ClawLink: paste your Rkvst key once and 24 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/rkvst The usual route to Rkvst 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 Rkvst setup: install one ClawHub skill, connect Rkvst in the browser, and OpenClaw can call real Rkvst 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 Rkvst. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Rkvst** — 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 rkvst # connect Rkvst (browser OAuth) npx -y @useclawlink/cli actions rkvst # list available actions npx -y @useclawlink/cli run rkvst --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 Rkvst in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Rkvst API key once. Verify the connection by asking OpenClaw: > Use Rkvst to download event attachment 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Rkvst is connected in the dashboard, that agent calls the same 24 Rkvst 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). ## Rkvst MCP for OpenClaw Looking for a Rkvst MCP server for OpenClaw? ClawLink connects Rkvst to OpenClaw and exposes 24 Rkvst 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 Rkvst integration](https://claw-link.dev/hermes/rkvst) works the same way. ## What the OpenClaw Rkvst integration can do 24 Rkvst tools are ready for OpenClaw once the account is connected. ### All 24 Rkvst tools for OpenClaw | Tool | What it does | |---|---| | **Download event attachment** `rkvst_download_event_attachment` | Download an attachment from a specified Event on an Asset | | **Get app registration** `rkvst_get_app_registration` | Retrieve details for a given App Registration ID | | **Get asset** `rkvst_get_asset` | Retrieve details for a given Asset | | **Get blob** `rkvst_get_blob` | Retrieve details of a Blob by ID | | **Get event** `rkvst_get_event` | Retrieve details of a specified Event | | **Get iam subject** `rkvst_get_iam_subject` | Retrieve IAM subject details | | **Get member** `rkvst_get_member` | Retrieve details for a given Member ID | | **Get public asset** `rkvst_get_public_asset` | Retrieve details for a public asset | | **Get public asset event** `rkvst_get_public_asset_event` | Retrieve a specific public asset event | | **Get tenancy** `rkvst_get_tenancy` | Retrieve details for a specific tenancy | | **List app registrations** `rkvst_list_app_registrations` | List all App Registrations | | **List asset events** `rkvst_list_asset_events` | List events for a specified asset | | **List assets** `rkvst_list_assets` | List all Assets with optional pagination and filters | | **List iam subjects** `rkvst_list_iam_subjects` | List IAM subjects | | **List members** `rkvst_list_members` | List all tenant Members | | **List public asset events** `rkvst_list_public_asset_events` | List events for a specific public asset | | **List public assets** `rkvst_list_public_assets` | List all Public Assets | | **List tenancies** `rkvst_list_tenancies` | List all tenancies | | **Retrieve asset attachment metadata** `rkvst_retrieve_asset_attachment_metadata` | Retrieve metadata for an attachment on a specified Asset | | **Retrieve caps** `rkvst_retrieve_caps` | Retrieve resource limit quotas for a specified service | | **Retrieve event attachment metadata** `rkvst_retrieve_event_attachment_metadata` | Retrieve metadata for an attachment on a specified Event | | **Search events** `rkvst_search_events` | Search events matching filter criteria with pagination | | **Promote member** `rkvst_promote_member` | Promote a tenant member to OWNER role | | **Update app registration** `rkvst_update_app_registration` | Update an application's display name or custom claims | ## Example prompts **Download Event Attachment** > Use Rkvst to download event attachment and walk me through the result in plain English. **Get App Registration** > Pull the relevant data from Rkvst, summarize it in plain English, and point out anything that needs attention. **Get Asset** > Pull the relevant data from Rkvst, summarize it in plain English, and point out anything that needs attention. **Get Blob** > Pull the relevant data from Rkvst, 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Rkvst working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Rkvst API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Rkvst 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 Rkvst. | 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 Rkvst actions to the runtime in a format your agent can reliably use. | 24 tools for Rkvst are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Rkvst 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 Rkvst in the browser, and the 24 tools above work from chat. There is no SDK and no config file, and the Rkvst 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 Rkvst skill but can't call the tools The ClawHub skill teaches OpenClaw about Rkvst, but the calls run through the ClawLink plugin and your connected account. Make sure Rkvst 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 Rkvst 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 Rkvst tools Rkvst 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 Rkvst 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. ### Rkvst 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 Rkvst has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Rkvst integration? Yes. ClawLink is the fastest way to connect OpenClaw to Rkvst: link your Rkvst account once in the browser and OpenClaw can call the Rkvst API through 24 ready-made tools — no custom code or token handling. ### How do I add Rkvst to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Rkvst skill from ClawHub, then you click Connect in the dashboard to authorize Rkvst. OpenClaw calls the tools from the next message — no config files, and the Rkvst key you paste is stored server-side instead of in your environment. ### How long does it take to connect Rkvst to OpenClaw? About two minutes. Sign in, click Connect next to Rkvst in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Rkvst 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 Rkvst working from chat. ### OpenClaw installed the Rkvst skill but can't call the tools The ClawHub skill teaches OpenClaw about Rkvst, but the calls run through the ClawLink plugin and your connected account. Make sure Rkvst 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 - [GitHub](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [OpenClaw PagerDuty integration](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [OpenClaw SafetyCulture integration](https://claw-link.dev/openclaw/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.