# How to connect Langbase to OpenClaw (paste one key, 20 tools) > Connect Langbase to OpenClaw with ClawLink: paste your Langbase key once and 20 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/langbase The usual route to Langbase 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 Langbase setup: install one ClawHub skill, connect Langbase in the browser, and OpenClaw can call real Langbase 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 Langbase. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Langbase** — 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 langbase # connect Langbase (browser OAuth) npx -y @useclawlink/cli actions langbase # list available actions npx -y @useclawlink/cli run langbase --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 Langbase in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Langbase API key once. Verify the connection by asking OpenClaw: > Use Langbase to check health 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 Langbase is connected in the dashboard, that agent calls the same 20 Langbase 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). ## Langbase MCP for OpenClaw Looking for a Langbase MCP server for OpenClaw? ClawLink connects Langbase to OpenClaw and exposes 20 Langbase 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 Langbase integration](https://claw-link.dev/hermes/langbase) works the same way. ## What the OpenClaw Langbase integration can do 20 Langbase tools are ready for OpenClaw once the account is connected. The 17 below are the ones people reach for most; your agent can call all 20. ### 17 of 20 Langbase tools for OpenClaw | Tool | What it does | |---|---| | **Check health** `langbase_check_health` | Check the health status of the Langbase API service | | **Chunker split content** `langbase_chunker_split_content` | Split content into smaller chunks | | **Document list** `langbase_document_list` | List documents in a specific memory | | **Get pipe** `langbase_get_pipe` | Retrieve details of a specific pipe by owner and name | | **Get thread** `langbase_get_thread` | Retrieve details of a specific conversation thread | | **List models** `langbase_list_models` | Get available AI models supported by Langbase | | **List thread messages** `langbase_list_thread_messages` | List all messages in a conversation thread | | **List traces** `langbase_list_traces` | Get execution traces for debugging and monitoring pipe runs | | **Memory list** `langbase_memory_list` | List all memory objects | | **Pipe list** `langbase_pipe_list` | List all pipes | | **Append thread messages** `langbase_append_thread_messages` | Add new messages to an existing conversation thread | | **Create thread** `langbase_create_thread` | Create a new conversation thread | | **Memory create** `langbase_memory_create` | Create a new memory | | **Pipe create** `langbase_pipe_create` | Create a new pipe | | **Update pipe** `langbase_update_pipe` | Update an existing pipe's configuration on Langbase | | **Update thread** `langbase_update_thread` | Update an existing thread's metadata | | **Update thread message** `langbase_update_thread_message` | Update an existing message in a conversation thread | ## Example prompts **Check Health** > Use Langbase to check health and walk me through the result in plain English. **Chunker Split Content** > Use Langbase to chunker split content and walk me through the result in plain English. **Document List** > Use Langbase to document list and walk me through the result in plain English. **Get Pipe** > Pull the relevant data from Langbase, 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 Langbase working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Langbase API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Langbase 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 Langbase. | 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 Langbase actions to the runtime in a format your agent can reliably use. | 20 tools for Langbase are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Langbase 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 Langbase in the browser, and the 20 tools above work from chat. There is no SDK and no config file, and the Langbase 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 Langbase skill but can't call the tools The ClawHub skill teaches OpenClaw about Langbase, but the calls run through the ClawLink plugin and your connected account. Make sure Langbase 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 Langbase 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 Langbase tools Langbase 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 Langbase 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. ### Langbase 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 Langbase has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Langbase integration? Yes. ClawLink is the fastest way to connect OpenClaw to Langbase: link your Langbase account once in the browser and OpenClaw can call the Langbase API through 20 ready-made tools — no custom code or token handling. ### How do I add Langbase to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Langbase skill from ClawHub, then you click Connect in the dashboard to authorize Langbase. OpenClaw calls the tools from the next message — no config files, and the Langbase key you paste is stored server-side instead of in your environment. ### How long does it take to connect Langbase to OpenClaw? About two minutes. Sign in, click Connect next to Langbase in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Langbase 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 Langbase working from chat. ### OpenClaw installed the Langbase skill but can't call the tools The ClawHub skill teaches OpenClaw about Langbase, but the calls run through the ClawLink plugin and your connected account. Make sure Langbase 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 DataRobot integration](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. - [Connect 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.