How to integrate Conductor MCP with OpenClaw

OpenClaw is the fastest growing agent harness out there, which can work 24/7 to automate almost any kind of tasks. However, its capabilities are limited to the tools it has access to. Composio allows your OpenClaw to access Conductor with authentication management handled for you. You can execute actions on Conductor via your favorite OpenClaw interface (Telegram, WhatsApp, TUI, etc), whichever you prefer.

Conductor logoConductor
Api Key

Conductor is a cloud development platform for workspaces, coding-agent sessions, messages, and transcript search. It helps teams run, review, and coordinate agent-driven development in one place.

17 Tools

Introduction

OpenClaw is the fastest growing agent harness out there, which can work 24/7 to automate almost any kind of tasks. However, its capabilities are limited to the tools it has access to. Composio allows your OpenClaw to access Conductor with authentication management handled for you. You can execute actions on Conductor via your favorite OpenClaw interface (Telegram, WhatsApp, TUI, etc), whichever you prefer.

Also integrate Conductor with

Why use Composio?

Apart from a managed and hosted MCP server, you will get:

  • Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Handling Large tool responses out of LLM context to minimize context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

How to install Conductor with OpenClaw

Using Composio API Key and Setup Prompt

Copy the setup prompt from the OpenClaw dashboard
  • Run it in your OpenClaw chat interface.
  • Authenticate Conductor from the dashboard
  • Go back to your OpenClaw interface and start asking questions.

Using OpenClaw/Composio Plugin

1. Install OpenClaw Composio plugin

bash
openclaw plugins install @composio/openclaw-plugin

2. Copy the API Key from dashboard.composio.dev

3. Setup OpenClaw Config

bash
openclaw config set plugins.entries.composio.config.consumerKey "ck_your_key_here"

4. Restart OpenClaw

bash
openclaw gateway restart

5. Go to your chat interface and start asking questions.

6. When prompted, authenticate the app and you're all set.

How It Works

The plugin connects to Composio's MCP server at https://connect.composio.dev/mcp and registers all available tools directly into the OpenClaw agent. Tools are called by name — no extra search or execute steps needed.

If a tool returns an auth error, the agent will prompt you to connect that toolkit at dashboard.composio.dev.

Configuration

bash
{
  "plugins": {
    "entries": {
      "composio": {
        "enabled": true,
        "config": {
          "consumerKey": "ck_your_key_here"
        }
      }
    }
  }
}
OptionDescriptionDefault
enabledEnable or disable the plugintrue
consumerKeyYour Composio consumer key (ck_...)—
mcpUrlMCP server URL (advanced)https://connect.composio.dev/mcp

What is the Conductor MCP server, and what's possible with it?

The Conductor MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Conductor account. It provides structured and secure access to your projects, cloud workspaces, coding-agent sessions, messages, and transcripts, so your agent can create workspaces, run sessions, exchange messages, manage workspace states, and search transcripts on your behalf.

  • Cloud workspace management: Have your agent create workspaces for available projects, check their status, rename them, or put them to sleep or archive them.
  • Coding-agent session control: Let the agent create and rename sessions, check whether they are idle, working, or in an error state, and stop current work or archive sessions.
  • Agent messaging: Direct your agent to send coding prompts to a session and read individual messages or full session conversations.
  • Transcript search and review: Instruct your agent to search session transcripts with read-only queries and find relevant details from past coding work.
  • Project and activity discovery: Have your agent list available repository projects, browse their workspaces and sessions, and review recent activity.

Conclusion

You've successfully integrated Conductor with OpenClaw using Composio plugin. Now interact with Conductor directly from your terminal, Web UI, or any messenger app using natural language commands.

Key benefits of this setup:

  • Seamless integration across TUI, Web UIs, and Messenger apps like Telegram, WhatsApp, Slack, etc.
  • Natural language commands for Conductor operations
  • Managed authentication through Composio
  • Access to 20,000+ tools across 1000+ apps for cross-app workflows
  • Programmatic tool calling for complex tool chaining

Next steps:

  • Try asking OpenClaw to perform various Conductor operations
  • Explore cross-app workflows by connecting more toolkits like Calendar, Slack, Notion, etc.
  • Build complex automation scripts that leverage OpenClaw's 24/7 running capabilities
TOOLS

Supported Tools

Every Conductor action and event your agent gets out of the box.

Change Workspace State

Put a workspace to sleep or archive it.

Create Session

Create another agent chat session in an existing workspace.

Create Workspace

Create a cloud workspace and its first agent session.

Get Current User

Return the user and organization represented by the connected Conductor API key.

Get Message

Get one transcript message by id.

Get Project

Get one Conductor project and its repository remote by project id.

Get Session

Get one agent session's configuration and current idle, working, or error status in one read.

Get Workspace

Get a workspace's metadata and current lifecycle status in one read, including initialization progress or errors.

List Messages

Read one page of a session transcript or incrementally read messages after a known message ID.

List Projects

List repositories available to the connected account for creating Conductor workspaces.

List Sessions

List one page of agent chat sessions in a Conductor workspace.

List Workspaces

List one page of workspaces belonging to a Conductor project, including deep links and recent activity.

Query Transcripts

Run one read-only SQL SELECT against the organization's session_transcripts_view.

Rename Session

Change an existing Conductor session's display name without stopping its agent.

Rename Workspace

Change the display name of an existing Conductor workspace without changing its lifecycle state.

Send Message

Send a prompt to a Conductor session agent.

Stop Session

Cancel only the current turn and queued messages, or archive the entire session.

FAQ

Frequently asked questions

With a standalone Conductor MCP server, the agents and LLMs can only access a fixed set of Conductor tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Conductor and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. OpenClaw fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Conductor tools.

Yes, absolutely. You can configure which Conductor scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Conductor data and credentials are handled as safely as possible.

Start with Conductor.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Conductor tool your agent needs.Free to start.

Start building