Skip to content

Connect Linear to Conductor

Issue tracker for product teams. Its hosted MCP server lets agents find, create and update issues, projects and comments, so design tasks stay linked to the work.

MCP serverOfficialChecked 2026-11-16

Before you start

  • Conductor installed (see its MCP documentation (opens in a new tab)).
  • Linear is available on macOS, Windows, Linux and the web.
  • Your agent opens a Linear sign-in page the first time it connects. For read-only access, use https://mcp.linear.app/mcp/readonly instead.
  1. Step 1: Add Linear to Conductor

    For Claude Code sessions

    Saves the server to your Claude Code user settings, so every Conductor workspace gets it.

    Terminal
    claude mcp add --scope user --transport http linear https://mcp.linear.app/mcp

    For Codex sessions

    Saves the server to ~/.codex/config.toml, which Codex sessions in every workspace read.

    Terminal
    codex mcp add linear --url https://mcp.linear.app/mcp

    Or share it with your team

    Add this to .mcp.json at the project root and commit it. Claude Code sessions in every workspace on that branch pick it up.

    .mcp.json
    {
      "mcpServers": {
        "linear": {
          "type": "http",
          "url": "https://mcp.linear.app/mcp"
        }
      }
    }

    Or edit Codex's config file

    Add this to ~/.codex/config.toml.

    ~/.codex/config.toml
    [mcp_servers.linear]
    url = "https://mcp.linear.app/mcp"
    Good to know
    • Start a new session in Conductor after adding a server, so the agent loads it.
    • To sign in, open Conductor's MCP status dialog and use the sign-in action on the server's row.
  2. Step 2: Check it's connected

    Terminal
    claude mcp list

    In a Conductor session, click the plug icon in the composer or run /mcp-status to see each server's status.

  3. Step 3: Try a first request

    Ask Conductor something that only works with Linear connected:

    Say to Conductor
    Find the Linear issues assigned to me that mention design and list them by priority.

If it doesn't work

  • Conductor has no MCP settings of its own. Claude Code and Codex sessions load the same servers they use outside Conductor.
  • Each workspace is a separate git worktree. Servers added with plain claude mcp add only apply to the folder you ran it in, so use --scope user or a committed .mcp.json.
  • Conductor runs on macOS. Environment variables for local servers can go in .conductor/settings.local.toml, under [environment_variables].