conductorv2

Integrations · AI Clients

Cursor

Add Conductor via Cursor's Settings panel or a .cursor/mcp.json file in your project.

Setup via Settings UI

1Open Cursor. Go to Settings (⌘, or Ctrl+,).
2Navigate to Features → MCP Servers.
3Click Add new MCP server.
4Set name: conductor, type: command, command: npx -y @useconductor/conductor
5Click Save. Cursor will start Conductor immediately — no restart needed.

Setup via config file

Cursor reads MCP config from ~/.cursor/mcp.json (global) or .cursor/mcp.json in the project root. Create or edit the global file:

~/.cursor/mcp.json
{
  "mcpServers": {
    "conductor": {
      "command": "npx",
      "args": ["-y", "@useconductor/conductor"]
    }
  }
}
.cursor/mcp.json — project-level, commit to repo
// .cursor/mcp.json — in repo root, shared with team
{
  "mcpServers": {
    "conductor": {
      "command": "npx",
      "args": ["-y", "@useconductor/conductor"]
    }
  }
}

With environment variables

~/.cursor/mcp.json
{
  "mcpServers": {
    "conductor": {
      "command": "npx",
      "args": ["-y", "@useconductor/conductor"],
      "env": {
        "GITHUB_TOKEN": "ghp_your_token",
        "CONDUCTOR_LOG_LEVEL": "info"
      }
    }
  }
}

Enabling MCP in Cursor Agent

MCP tools are available in Cursor's Agent mode (the chat panel). Make sure you're using Agent, not Chat — only Agent has tool use. In the chat panel, look for the agent toggle or @conductor mentions.

Mode requiredAgent (not Chat or Edit)
Enable MCPSettings → Features → Enable MCP (should be on by default)
See active toolsIn agent chat, click the tools icon to see all available MCP tools

Troubleshooting

Conductor not showing in MCP server list

Check the config file syntax (valid JSON). Cursor shows a red indicator next to servers that failed to start — hover it for the error.

Server shows as started but no tools

Conductor may have crashed on startup. Check ~/.conductor/logs/error.log. Often a config validation error.

npx hangs on first run

First run downloads the package — takes a few seconds. If it hangs more than 30s, check your npm registry connectivity: npm ping

Works globally but not in project

Project .cursor/mcp.json overrides the global config entirely. Make sure the project file has the conductor entry.

Cursor uses an old Conductor version

npx -y always installs the latest. If you pinned a version, update it. Run: npx @useconductor/conductor --version to check.