Skip to main content
Conductor does not try to replace the rest of your toolchain. It coordinates it.

Connect tools without losing the control plane

Integrations should extend visibility and automation around the runtime. They should not become a second system for task state, repo truth, or review routing.

GitHub + CIMCP clientsEditor handoffWebhook automation
Conductor remote control dashboard
Core integration areas:
  • GitHub for repo and PR workflows
  • MCP clients for editor and assistant access
  • editor deep links for browser-to-code handoff
  • notification plugins for lifecycle updates
  • webhook and MCP server entrypoints for automation

GitHub

Connect pull requests, CI visibility, issues, and review state to the repositories Conductor is actually operating on.

MCP Clients

Call the orchestrator from Cursor, Claude Desktop, and other MCP-aware tools.

Editor Handoff

Jump from the browser into the correct worktree and file context in VS Code or Cursor.

Webhook Automation

Trigger tasks over HTTP and route repository events into the board without building a second control plane.

​
Start with these pages

Last modified on March 6, 2026