conductorv2

Integrations · AI Clients

Claude Code

One command. Conductor works with Claude Code out of the box — no config file editing, no JSON, no restart required.

Setup — one command

Run this once in any terminal. Claude Code registers Conductor immediately — it's available in the current session and all future sessions.

terminal
claude mcp add conductor -- npx -y @useconductor/conductor

This uses npx — no global install needed. Conductor downloads and runs on first use.

Setup — with global install

If you installed Conductor globally with npm, register the binary directly. Slightly faster startup since it skips npx resolution.

terminal
# Install globally first (optional — npx works without it)
npm install -g @useconductor/conductor

# Then register with Claude Code
claude mcp add conductor -- conductor mcp start

Verify it worked

terminal
# List all registered MCP servers
claude mcp list

# Should show:
# conductor    npx -y @useconductor/conductor    enabled

Or ask Claude Code directly:

test prompts
# These prompts verify specific plugins are working:

"List the files in the current directory"
→ Uses filesystem.list

"What's the git status of this repo?"
→ Uses git.status

"Run: echo hello"
→ Uses shell.exec (will ask for approval first)

"Search for TODO comments in src/"
→ Uses filesystem.search

Passing environment variables

Plugin credentials (GitHub token, Slack token, etc.) can be passed directly through Claude Code's MCP config using -e flags. These are stored securely and passed to the Conductor process at startup.

with env vars
# Pass environment variables to Conductor from Claude Code
claude mcp add conductor \
  -e GITHUB_TOKEN=ghp_... \
  -e SLACK_BOT_TOKEN=xoxb-... \
  -- npx -y @useconductor/conductor

Scope — global vs project

By default, claude mcp add registers globally (all projects). Use --scope project to create a .mcp.json file in the repo — commit it to share Conductor with your team.

scope options
# Add to current project only (creates .mcp.json in repo root)
claude mcp add conductor --scope project -- npx -y @useconductor/conductor

# Add globally for all projects (default)
claude mcp add conductor --scope global -- npx -y @useconductor/conductor

# Add for current user only
claude mcp add conductor --scope user -- npx -y @useconductor/conductor
.mcp.json — commit to repo
// .mcp.json — committed to repo, shared with team
{
  "mcpServers": {
    "conductor": {
      "command": "npx",
      "args": ["-y", "@useconductor/conductor"]
    }
  }
}

Managing Conductor in Claude Code

claude mcp listShow all registered MCP servers and their status
claude mcp add conductor -- npx -y @useconductor/conductorRegister Conductor (run once)
claude mcp remove conductorUnregister Conductor
claude mcp get conductorShow Conductor's full config

Troubleshooting

Tools don't appear after running claude mcp add

Claude Code picks up MCP servers on next invocation — no restart needed. Just start a new conversation and ask Claude to list files.

"npx: command not found"

npx ships with Node.js. Install Node.js 18+ from nodejs.org, then try again.

Conductor starts but shows 0 tools

Run conductor doctor to check plugin status. A plugin config error can prevent tools from registering.

Shell commands always rejected

The shell plugin requires an allowlist. Run: conductor config setup shell — or add allowedCommands to ~/.conductor/config.json.

Works in one project, not another

You may have registered with --scope project. Run claude mcp add --scope global to make it available everywhere.