How to connect Conductor to OpenClaw
Connect Conductor to OpenClaw with ClawLink: paste your Conductor key once and 17 tools work from chat. No MCP server to run, nothing stored on your machine.
ConductorAPI KEYMCPConductor is a cloud development platform for creating workspaces, running coding-agent sessions, exchanging messages, and searching session transcripts.. Once connected, OpenClaw can read and act on Conductor from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Conductor 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 Conductor setup: install one ClawHub skill, connect Conductor in the browser, and OpenClaw can call real Conductor 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 Conductor.
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 Conductor
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Conductor?"
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 Conductor in the ClawLink dashboard — paste your Conductor API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Conductor, 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 Conductor is connected in the dashboard, that agent calls the same 17 Conductor tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Conductor MCP for OpenClaw
Looking for a Conductor MCP server for OpenClaw? ClawLink connects Conductor to OpenClaw and exposes 17 Conductor tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Conductor integration works the same way.
What the OpenClaw Conductor integration can do
17 Conductor tools are ready for OpenClaw once the account is connected.
All 17 Conductor tools for OpenClaw
| Tool | What it does |
|---|---|
Get current user conductor_get_current_user | Return the user and organization represented by the connected Conductor API key |
Get message conductor_get_message | Get one transcript message by id |
Get project conductor_get_project | Get one Conductor project and its repository remote by project id |
Get session conductor_get_session | Get one agent session's configuration and current idle, working, or error status in one read |
Get workspace conductor_get_workspace | Get a workspace's metadata and current lifecycle status in one read, including initialization |
List messages conductor_list_messages | Read one page of a session transcript or incrementally read messages after a known message ID |
List projects conductor_list_projects | List repositories available to the connected account for creating Conductor workspaces |
List sessions conductor_list_sessions | List one page of agent chat sessions in a Conductor workspace |
List workspaces conductor_list_workspaces | List one page of workspaces belonging to a Conductor project, including deep links and recent |
Query transcripts conductor_query_transcripts | Run one read-only SQL SELECT against the organization's session_transcripts_view |
Create session conductor_create_session | Create another agent chat session in an existing workspace |
Create workspace conductor_create_workspace | Create a cloud workspace and its first agent session |
Rename session conductor_rename_session | Change an existing Conductor session's display name without stopping its agent |
Rename workspace conductor_rename_workspace | Change the display name of an existing Conductor workspace without changing its lifecycle state |
Send message conductor_send_message | Send a prompt to a Conductor session agent |
Change workspace state conductor_change_workspace_state | Put a workspace to sleep or archive it |
Stop session conductor_stop_session | Cancel only the current turn and queued messages, or archive the entire session |
Try it: find the Conductor tool you need
Browse the 17 Conductor 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 Conductor, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Conductor, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Conductor, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Conductor, 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 Conductor working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Conductor API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Conductor 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 Conductor. | 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 Conductor actions to the runtime in a format your agent can reliably use. | 17 tools for Conductor are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Conductor 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 Conductor in the browser, and the 17 tools above work from chat. There is no SDK and no config file, and the Conductor 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 Conductor skill but can't call the tools
The ClawHub skill teaches OpenClaw about Conductor, but the calls run through the ClawLink plugin and your connected account. Make sure Conductor 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 Conductor 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 Conductor tools
Conductor 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 Conductor 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.
Conductor 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 Conductor 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 Conductor integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Conductor: link your Conductor account once in the browser and OpenClaw can call the Conductor API through 17 ready-made tools — no custom code or token handling.
How do I add Conductor to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Conductor skill from ClawHub, then you click Connect in the dashboard to authorize Conductor. OpenClaw calls the tools from the next message — no config files, and the Conductor key you paste is stored server-side instead of in your environment.
How long does it take to connect Conductor to OpenClaw?
About two minutes. Sign in, click Connect next to Conductor in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Conductor 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 Conductor working from chat.
OpenClaw installed the Conductor skill but can't call the tools
The ClawHub skill teaches OpenClaw about Conductor, but the calls run through the ClawLink plugin and your connected account. Make sure Conductor 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 tools
DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets.
Chatbotkit tools
ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications.
Connect Just One API
Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.