# How to connect Orgo to OpenClaw (paste one key, 11 tools) > Connect Orgo to OpenClaw with ClawLink: paste your Orgo key once and 11 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/orgo The usual route to Orgo 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 Orgo setup: install one ClawHub skill, connect Orgo in the browser, and OpenClaw can call real Orgo 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 Orgo. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Orgo** — 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 orgo # connect Orgo (browser OAuth) npx -y @useclawlink/cli actions orgo # list available actions npx -y @useclawlink/cli run orgo --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 Orgo in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Orgo API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Orgo, 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 Orgo is connected in the dashboard, that agent calls the same 11 Orgo 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). ## Orgo MCP for OpenClaw Looking for a Orgo MCP server for OpenClaw? ClawLink connects Orgo to OpenClaw and exposes 11 Orgo 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 Orgo integration](https://claw-link.dev/hermes/orgo) works the same way. ## What the OpenClaw Orgo integration can do 11 Orgo tools are ready for OpenClaw once the account is connected. The 10 below are the ones people reach for most; your agent can call all 11. ### 10 of 11 Orgo tools for OpenClaw | Tool | What it does | |---|---| | **Get computer** `orgo_get_computer` | Get current details and status for one Orgo computer | | **Get screenshot** `orgo_get_screenshot` | Capture the current display of a running Orgo computer for visual inspection before deciding on | | **List templates** `orgo_list_templates` | List either templates owned by the connected account or Orgo-maintained curated templates | | **List workspaces** `orgo_list_workspaces` | List workspaces accessible to the connected Orgo key, including the computers in each workspace | | **Create computer** `orgo_create_computer` | Create and automatically start a virtual computer in an accessible workspace | | **Control pointer** `orgo_control_pointer` | Perform one pointer action on a running Orgo computer: click, drag, or scroll | | **Execute code** `orgo_execute_code` | Execute arbitrary Bash or Python code on an Orgo computer | | **Run computer agent** `orgo_run_computer_agent` | Run one non-streaming computer-use agent task on a running Orgo computer | | **Send keyboard input** `orgo_send_keyboard_input` | Send either literal text or one key or key combination to the current keyboard focus on a | | **Set computer power state** `orgo_set_computer_power_state` | Start, stop, or restart one Orgo computer after explicit user confirmation | ## Example prompts **Get Computer** > Pull the relevant data from Orgo, summarize it in plain English, and point out anything that needs attention. **Get Screenshot** > Pull the relevant data from Orgo, summarize it in plain English, and point out anything that needs attention. **List Templates** > List the relevant items in Orgo, group them by priority, and recommend what OpenClaw should do next. **List Workspaces** > List the relevant items in Orgo, 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 Orgo working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Orgo API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Orgo 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 Orgo. | 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 Orgo actions to the runtime in a format your agent can reliably use. | 11 tools for Orgo are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Orgo 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 Orgo in the browser, and the 11 tools above work from chat. There is no SDK and no config file, and the Orgo 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 Orgo skill but can't call the tools The ClawHub skill teaches OpenClaw about Orgo, but the calls run through the ClawLink plugin and your connected account. Make sure Orgo 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 Orgo 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 Orgo tools Orgo 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 Orgo 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. ### Orgo 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 Orgo has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Orgo integration? Yes. ClawLink is the fastest way to connect OpenClaw to Orgo: link your Orgo account once in the browser and OpenClaw can call the Orgo API through 11 ready-made tools — no custom code or token handling. ### How do I add Orgo to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Orgo skill from ClawHub, then you click Connect in the dashboard to authorize Orgo. OpenClaw calls the tools from the next message — no config files, and the Orgo key you paste is stored server-side instead of in your environment. ### How long does it take to connect Orgo to OpenClaw? About two minutes. Sign in, click Connect next to Orgo in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Orgo 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 Orgo working from chat. ### OpenClaw installed the Orgo skill but can't call the tools The ClawHub skill teaches OpenClaw about Orgo, but the calls run through the ClawLink plugin and your connected account. Make sure Orgo 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. - [Just One API tools](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.