Integrations · AI Clients
Cursor
Add Conductor via Cursor's Settings panel or a .cursor/mcp.json file in your project.
Setup via Settings UI
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:
{
"mcpServers": {
"conductor": {
"command": "npx",
"args": ["-y", "@useconductor/conductor"]
}
}
}// .cursor/mcp.json — in repo root, shared with team
{
"mcpServers": {
"conductor": {
"command": "npx",
"args": ["-y", "@useconductor/conductor"]
}
}
}With environment variables
{
"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.
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.