Skip to content

Connect GitHub MCP to Conductor

GitHub's official MCP server. Agents can read code, issues and pull requests, open PRs and leave reviews, so a design change can go from canvas to merged code.

MCP serverOfficialChecked 2026-11-16

Before you start

  • Conductor installed (see its MCP documentation (opens in a new tab)).
  • GitHub MCP is available on macOS, Windows and Linux.
  • This setup runs GitHub's Docker image, so Docker must be installed and running. Create a fine-grained personal access token with only the repositories and permissions you need, and set it as GITHUB_PERSONAL_ACCESS_TOKEN in your environment. To skip Docker, use GitHub MCP (remote), the hosted version.
  1. Step 1: Add GitHub MCP 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 github -e 'GITHUB_PERSONAL_ACCESS_TOKEN=${GITHUB_PERSONAL_ACCESS_TOKEN}' -- docker run -i --rm -e GITHUB_PERSONAL_ACCESS_TOKEN ghcr.io/github/github-mcp-server

    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": {
        "github": {
          "type": "stdio",
          "command": "docker",
          "args": [
            "run",
            "-i",
            "--rm",
            "-e",
            "GITHUB_PERSONAL_ACCESS_TOKEN",
            "ghcr.io/github/github-mcp-server"
          ],
          "env": {
            "GITHUB_PERSONAL_ACCESS_TOKEN": "${GITHUB_PERSONAL_ACCESS_TOKEN}"
          }
        }
      }
    }

    Or edit Codex's config file

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

    ~/.codex/config.toml
    [mcp_servers.github]
    command = "docker"
    args = ["run", "-i", "--rm", "-e", "GITHUB_PERSONAL_ACCESS_TOKEN", "ghcr.io/github/github-mcp-server"]
    env_vars = ["GITHUB_PERSONAL_ACCESS_TOKEN"]
    Good to know
    • Start a new session in Conductor after adding a server, so the agent loads it.
    • Claude Code reads the ${NAME} values from your environment when the server starts.
    • env_vars passes those variables from your environment to the server, so their values stay out of the file.
  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 GitHub MCP connected:

    Say to Conductor
    List the open pull requests in this repository and summarise what the newest one changes.

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].