How to connect Conductor to Claude

Connect Claude Web, Desktop and Cowork to Conductor MCP. Create a workspace for bug triage, start a coding agent refactor session, and more using natural language, with authentication handled for you.

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

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your Conductor account to Claude via Composio Connect, enabling it to create a workspace for bug triage, start a coding agent refactor session, search transcripts for failed deploy discussion, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate Conductor with

Connecting Conductor to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your Conductor account

Back in Claude, ask it to connect to Conductor or give it any Conductor-related task.

For example, ask Claude to:

  • "Create a workspace for bug triage"
  • "Start a coding agent refactor session"
  • "Search transcripts for failed deploy discussion"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your Conductor account is ready to use.

What is the Conductor Claude Connector, 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 so your agent can perform Conductor operations on your behalf.

Troubleshooting

1. Why does Claude not use the Composio connector for Conductor?

The connector can show as connected, but Claude must use it in each Conductor conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to Conductor again.

2. Why does Claude show an MCP server error before Conductor connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Conductor.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect Conductor.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Conductor authorization link not work?

The Composio connector is one server. Your Conductor account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the Conductor connection.
  • Composio creates a fresh Conductor authorization link.
  • Open that link in your browser and finish the Conductor sign-in.

4. Why do Conductor actions fail after they worked before?

The Conductor connection can expire or lose permission.

  • Ask Claude to inspect the Conductor connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the Conductor account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in Conductor.
  • If the action still fails with a permission error, check that the connected account has that permission in Conductor itself.

5. How do I switch to a different Conductor account?

Claude can manage the Conductor connection for you.

  • Ask Claude to disconnect or delete the current Conductor account.
  • Ask Claude to connect Conductor again.
  • Open the new Composio authorization link for Conductor.
  • Sign in with the other Conductor account in the browser.
  • After the account connects, ask Claude to retry the Conductor task.

6. Why is my Conductor connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Conductor connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click and click Clear cache.
  • If Conductor tools still do not appear, click , disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Conductor.
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. Claude Cowork 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