Skip to content

Connect GitHub MCP (remote) to Conductor

GitHub's hosted MCP server. Agents read code, issues and pull requests and open PRs with nothing to run on your machine, connecting with a personal access token.

MCP serverOfficialChecked 2026-11-16

Before you start

  • Conductor installed (see its MCP documentation (opens in a new tab)).
  • GitHub MCP (remote) is available on macOS, Windows, Linux and the web.
  • 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. For read-only tools, end the URL with /readonly. GitHub Enterprise Server doesn't support the hosted server.
  1. Step 1: Add GitHub MCP (remote) 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 github-remote https://api.githubcopilot.com/mcp/ --header 'Authorization: Bearer ${GITHUB_PERSONAL_ACCESS_TOKEN}'

    For Codex sessions

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

    Terminal
    codex mcp add github-remote --url https://api.githubcopilot.com/mcp/ --bearer-token-env-var GITHUB_PERSONAL_ACCESS_TOKEN

    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-remote": {
          "type": "http",
          "url": "https://api.githubcopilot.com/mcp/",
          "headers": {
            "Authorization": "Bearer ${GITHUB_PERSONAL_ACCESS_TOKEN}"
          }
        }
      }
    }

    Or edit Codex's config file

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

    ~/.codex/config.toml
    [mcp_servers.github-remote]
    url = "https://api.githubcopilot.com/mcp/"
    bearer_token_env_var = "GITHUB_PERSONAL_ACCESS_TOKEN"
    Good to know
    • Start a new session in Conductor after adding a server, so the agent loads it.
    • Set GITHUB_PERSONAL_ACCESS_TOKEN in your environment before you start Claude Code. It reads the value each time it connects, so the token stays out of the config.
    • Codex reads GITHUB_PERSONAL_ACCESS_TOKEN from your environment each time it connects, so the token stays 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 (remote) connected:

    Say to Conductor
    List the open issues in this repository that mention design and group them by label.

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