How to connect Weights & Biases to OpenClaw
Connect Weights & Biases to OpenClaw with ClawLink: paste your Weights & Biases key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine.
Weights & BiasesAPI KEYMCPRead W&B Models projects, runs, sweeps, artifact types, reports, automations, integrations, teams, and organizations through the W&B Cloud GraphQL API.. Once connected, OpenClaw can read and act on Weights & Biases from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Weights & Biases 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 Weights & Biases setup: install one ClawHub skill, connect Weights & Biases in the browser, and OpenClaw can call real Weights & Biases 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 Weights & Biases.
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 Weights & Biases
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Weights & Biases?"
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 Weights & Biases in the ClawLink dashboard — paste your Weights & Biases API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Weights & Biases, 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Weights & Biases is connected in the dashboard, that agent calls the same 10 Weights & Biases tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Weights & Biases MCP for OpenClaw
Looking for a Weights & Biases MCP server for OpenClaw? ClawLink connects Weights & Biases to OpenClaw and exposes 10 Weights & Biases tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Weights & Biases integration works the same way.
What the OpenClaw Weights & Biases integration can do
10 Weights & Biases tools are ready for OpenClaw once the account is connected.
All 10 Weights & Biases tools for OpenClaw
| Tool | What it does |
|---|---|
Get current viewer weights_and_biases_get_current_viewer | Return the authenticated W&B user, default entity, and team names for connection context |
Get organization weights_and_biases_get_organization | Return a W&B organization's identifiers and organization entity by exact name |
Get team weights_and_biases_get_team | Return a W&B team's identity and bounded membership metadata by exact team entity name |
List artifact types weights_and_biases_list_artifact_types | Return one page of artifact types defined in a W&B project |
List automations weights_and_biases_list_automations | Return one page of W&B automations accessible under an entity |
List integrations weights_and_biases_list_integrations | List one page of Slack workspace/channel metadata and webhook integration names for a W&B entity |
List projects weights_and_biases_list_projects | Return one page of W&B projects visible under an entity |
List reports weights_and_biases_list_reports | Return one page of beta W&B reports for a project |
List runs weights_and_biases_list_runs | List one page of runs with IDs, display names, states, and creation times |
List sweeps weights_and_biases_list_sweeps | Return one page of hyperparameter sweeps from a W&B project when sweeps are enabled for the |
Try it: find the Weights & Biases tool you need
Browse the 10 Weights & Biases tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Weights & Biases, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Weights & Biases, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Weights & Biases, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Weights & Biases, 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 Weights & Biases working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Weights & Biases API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Weights & Biases 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 Weights & Biases. | 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 Weights & Biases actions to the runtime in a format your agent can reliably use. | 10 tools for Weights & Biases are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Weights & Biases 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 Weights & Biases in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the Weights & Biases 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 Weights & Biases skill but can't call the tools
The ClawHub skill teaches OpenClaw about Weights & Biases, but the calls run through the ClawLink plugin and your connected account. Make sure Weights & Biases 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 Weights & Biases 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 Weights & Biases tools
Weights & Biases 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 Weights & Biases 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.
Weights & Biases 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 Weights & Biases 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 Weights & Biases integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Weights & Biases: link your Weights & Biases account once in the browser and OpenClaw can call the Weights & Biases API through 10 ready-made tools — no custom code or token handling.
How do I add Weights & Biases to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Weights & Biases skill from ClawHub, then you click Connect in the dashboard to authorize Weights & Biases. OpenClaw calls the tools from the next message — no config files, and the Weights & Biases key you paste is stored server-side instead of in your environment.
How long does it take to connect Weights & Biases to OpenClaw?
About two minutes. Sign in, click Connect next to Weights & Biases in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Weights & Biases 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 Weights & Biases working from chat.
OpenClaw installed the Weights & Biases skill but can't call the tools
The ClawHub skill teaches OpenClaw about Weights & Biases, but the calls run through the ClawLink plugin and your connected account. Make sure Weights & Biases 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.
