# How to connect Spydra to OpenClaw (paste one key, 10 tools) > Connect Spydra to OpenClaw with ClawLink: paste your Spydra key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/spydra The usual route to Spydra 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 Spydra setup: install one ClawHub skill, connect Spydra in the browser, and OpenClaw can call real Spydra 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 Spydra. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Spydra** — 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 spydra # connect Spydra (browser OAuth) npx -y @useclawlink/cli actions spydra # list available actions npx -y @useclawlink/cli run spydra --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 Spydra in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Spydra API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Spydra, 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 Spydra is connected in the dashboard, that agent calls the same 10 Spydra 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). ## Spydra MCP for OpenClaw Looking for a Spydra MCP server for OpenClaw? ClawLink connects Spydra to OpenClaw and exposes 10 Spydra 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 Spydra integration](https://claw-link.dev/hermes/spydra) works the same way. ## What the OpenClaw Spydra integration can do 10 Spydra tools are ready for OpenClaw once the account is connected. ### All 10 Spydra tools for OpenClaw | Tool | What it does | |---|---| | **Get asset** `spydra_get_asset` | Return detailed information for one OpenRWA asset, optionally including token or token-sale | | **Get asset status counts** `spydra_get_asset_status_counts` | Return asset counts grouped by publication status for the connected OpenRWA token store | | **List asset tokens** `spydra_list_asset_tokens` | Return the tokens associated with one OpenRWA asset | | **List assets** `spydra_list_assets` | Return one numbered page of draft or published assets in the connected OpenRWA token store | | **List chains** `spydra_list_chains` | Return supported OpenRWA blockchain networks and their public network, currency, status, and | | **List countries** `spydra_list_countries` | Return the complete OpenRWA country reference list, including ISO codes, currencies, languages | | **List investor tokens** `spydra_list_investor_tokens` | Return one numbered page of tokens held or invested in by a specific OpenRWA investor | | **List investor transactions** `spydra_list_investor_transactions` | Return one numbered page of mint, payout, burn, or token-creation transactions for a specific | | **List investors** `spydra_list_investors` | Return one numbered page of investors registered with the connected OpenRWA token store | | **List token sales** `spydra_list_token_sales` | Search and filter one numbered page of OpenRWA token sales available through the connected store | ## Example prompts **Get Asset** > Pull the relevant data from Spydra, summarize it in plain English, and point out anything that needs attention. **Get Asset Status Counts** > Pull the relevant data from Spydra, summarize it in plain English, and point out anything that needs attention. **List Asset Tokens** > List the relevant items in Spydra, group them by priority, and recommend what OpenClaw should do next. **List Assets** > List the relevant items in Spydra, 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 Spydra working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Spydra API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Spydra 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 Spydra. | 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 Spydra actions to the runtime in a format your agent can reliably use. | 10 tools for Spydra are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Spydra 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 Spydra in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the Spydra 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 Spydra skill but can't call the tools The ClawHub skill teaches OpenClaw about Spydra, but the calls run through the ClawLink plugin and your connected account. Make sure Spydra 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 Spydra 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 Spydra tools Spydra 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 Spydra 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. ### Spydra 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 Spydra has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Spydra integration? Yes. ClawLink is the fastest way to connect OpenClaw to Spydra: link your Spydra account once in the browser and OpenClaw can call the Spydra API through 10 ready-made tools — no custom code or token handling. ### How do I add Spydra to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Spydra skill from ClawHub, then you click Connect in the dashboard to authorize Spydra. OpenClaw calls the tools from the next message — no config files, and the Spydra key you paste is stored server-side instead of in your environment. ### How long does it take to connect Spydra to OpenClaw? About two minutes. Sign in, click Connect next to Spydra in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Spydra 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 Spydra working from chat. ### OpenClaw installed the Spydra skill but can't call the tools The ClawHub skill teaches OpenClaw about Spydra, but the calls run through the ClawLink plugin and your connected account. Make sure Spydra 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 GitHub integration](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty tools](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [Connect SafetyCulture](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.