# How to connect Humanloop to OpenClaw (paste one key, 4 tools) > Connect Humanloop to OpenClaw with ClawLink: paste your Humanloop key once and 4 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/humanloop The usual route to Humanloop 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 Humanloop setup: install one ClawHub skill, connect Humanloop in the browser, and OpenClaw can call real Humanloop actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/humanloop ## Setup It takes three steps to connect OpenClaw to Humanloop. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Humanloop** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **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 humanloop # connect Humanloop (browser OAuth) npx -y @useclawlink/cli actions humanloop # list available actions npx -y @useclawlink/cli run humanloop --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 Humanloop in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Humanloop API key once. Verify the connection by asking OpenClaw: > Create it in Humanloop for me, then confirm the important fields before you finish. ### 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 Humanloop is connected in the dashboard, that agent calls the same 4 Humanloop 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). ## Humanloop MCP for OpenClaw Looking for a Humanloop MCP server for OpenClaw? ClawLink connects Humanloop to OpenClaw and exposes 4 Humanloop 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 Humanloop integration](https://claw-link.dev/hermes/humanloop) works the same way. ## What the OpenClaw Humanloop integration can do 4 Humanloop tools are ready for OpenClaw once the account is connected. The 3 below are the ones people reach for most; your agent can call all 4. ### 3 of 4 Humanloop tools for OpenClaw | Tool | What it does | |---|---| | **Create project** `humanloop_create_project` | This tool creates a new project in Humanloop. It is an independent action that generates a project by accepting a project's name (required), an optional description, and an optional organization_id. | | **List experiments** `humanloop_list_experiments` | This tool retrieves an array of experiments associated with a specific project in Humanloop. | | **List sessions** `humanloop_list_sessions` | This tool retrieves a paginated list of sessions for a specific project in Humanloop. | ## Example prompts **Create Project** > Create it in Humanloop for me, then confirm the important fields before you finish. **List Experiments** > List the relevant items in Humanloop, group them by priority, and recommend what OpenClaw should do next. **List Sessions** > List the relevant items in Humanloop, 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 Humanloop working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Humanloop API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Humanloop 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 Humanloop. | 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 Humanloop actions to the runtime in a format your agent can reliably use. | 4 tools for Humanloop are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Humanloop 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 Humanloop in the browser, and the 4 tools above work from chat. There is no SDK and no config file, and the Humanloop 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 Humanloop skill but can't call the tools The ClawHub skill teaches OpenClaw about Humanloop, but the calls run through the ClawLink plugin and your connected account. Make sure Humanloop 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 Humanloop 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 Humanloop tools Humanloop 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 Humanloop 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. ### Humanloop 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 Humanloop has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Humanloop integration? Yes. ClawLink is the fastest way to connect OpenClaw to Humanloop: link your Humanloop account once in the browser and OpenClaw can call the Humanloop API through 4 ready-made tools — no custom code or token handling. ### How do I add Humanloop to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Humanloop skill from ClawHub, then you click Connect in the dashboard to authorize Humanloop. OpenClaw calls the tools from the next message — no config files, and the Humanloop key you paste is stored server-side instead of in your environment. ### How long does it take to connect Humanloop to OpenClaw? About two minutes. Sign in, click Connect next to Humanloop in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Humanloop 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 Humanloop working from chat. ### OpenClaw installed the Humanloop skill but can't call the tools The ClawHub skill teaches OpenClaw about Humanloop, but the calls run through the ClawLink plugin and your connected account. Make sure Humanloop 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 - [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. - [ElevenLabs](https://claw-link.dev/openclaw/elevenlabs) — Generate speech and voice cloning