# How to connect Openlayer to OpenClaw (paste one key, 10 tools) > Connect Openlayer to OpenClaw with ClawLink: paste your Openlayer 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/openlayer The usual route to Openlayer 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 Openlayer setup: install one ClawHub skill, connect Openlayer in the browser, and OpenClaw can call real Openlayer 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 Openlayer. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Openlayer** — 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 openlayer # connect Openlayer (browser OAuth) npx -y @useclawlink/cli actions openlayer # list available actions npx -y @useclawlink/cli run openlayer --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 Openlayer in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Openlayer API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Openlayer, 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 Openlayer is connected in the dashboard, that agent calls the same 10 Openlayer 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). ## Openlayer MCP for OpenClaw Looking for a Openlayer MCP server for OpenClaw? ClawLink connects Openlayer to OpenClaw and exposes 10 Openlayer 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 Openlayer integration](https://claw-link.dev/hermes/openlayer) works the same way. ## What the OpenClaw Openlayer integration can do 10 Openlayer tools are ready for OpenClaw once the account is connected. ### All 10 Openlayer tools for OpenClaw | Tool | What it does | |---|---| | **Get data source** `openlayer_get_data_source` | Return one Openlayer monitoring data source, including its backend, monitoring status, record | | **Get project version** `openlayer_get_project_version` | Return one Openlayer project commit or version with its processing status, commit metadata | | **Get workspace** `openlayer_get_workspace` | Return a workspace's identity, status, connected-account membership, usage counts, and plan | | **List data source test results** `openlayer_list_data_source_test_results` | Return one page of the latest monitoring test results for an Openlayer data source, optionally | | **List data sources** `openlayer_list_data_sources` | Return one page of monitoring data sources for an Openlayer project, optionally filtered by name | | **List project version test results** `openlayer_list_project_version_test_results` | Return one page of test results for a project version, optionally filtered by test category | | **List project versions** `openlayer_list_project_versions` | Return one page of commits and versions for an Openlayer project, including processing status | | **List projects** `openlayer_list_projects` | Return one page of projects visible to the connected Openlayer workspace, optionally filtered | | **List test results** `openlayer_list_test_results` | Return one page of results for a test, with optional project-version, data-source, and status | | **List tests** `openlayer_list_tests` | Return one page of tests configured for an Openlayer project, with filters for category | ## Example prompts **Get Data Source** > Pull the relevant data from Openlayer, summarize it in plain English, and point out anything that needs attention. **Get Project Version** > Pull the relevant data from Openlayer, summarize it in plain English, and point out anything that needs attention. **Get Workspace** > Pull the relevant data from Openlayer, summarize it in plain English, and point out anything that needs attention. **List Data Source Test Results** > List the relevant items in Openlayer, 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 Openlayer working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Openlayer API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Openlayer 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 Openlayer. | 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 Openlayer actions to the runtime in a format your agent can reliably use. | 10 tools for Openlayer are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Openlayer 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 Openlayer in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the Openlayer 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 Openlayer skill but can't call the tools The ClawHub skill teaches OpenClaw about Openlayer, but the calls run through the ClawLink plugin and your connected account. Make sure Openlayer 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 Openlayer 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 Openlayer tools Openlayer 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 Openlayer 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. ### Openlayer 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 Openlayer has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Openlayer integration? Yes. ClawLink is the fastest way to connect OpenClaw to Openlayer: link your Openlayer account once in the browser and OpenClaw can call the Openlayer API through 10 ready-made tools — no custom code or token handling. ### How do I add Openlayer to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Openlayer skill from ClawHub, then you click Connect in the dashboard to authorize Openlayer. OpenClaw calls the tools from the next message — no config files, and the Openlayer key you paste is stored server-side instead of in your environment. ### How long does it take to connect Openlayer to OpenClaw? About two minutes. Sign in, click Connect next to Openlayer in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Openlayer 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 Openlayer working from chat. ### OpenClaw installed the Openlayer skill but can't call the tools The ClawHub skill teaches OpenClaw about Openlayer, but the calls run through the ClawLink plugin and your connected account. Make sure Openlayer 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 - [Connect DataRobot](https://claw-link.dev/openclaw/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets. - [Chatbotkit](https://claw-link.dev/openclaw/chatbotkit) — ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications. - [Just One API](https://claw-link.dev/openclaw/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.