Skip to content

Connect GitHub MCP to Codex

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

  • Codex 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 Codex

    Add it to the 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
    • 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
    codex mcp list

    In a Codex session, run /mcp to see connected servers and their tools.

  3. Step 3: Try a first request

    Ask Codex something that only works with GitHub MCP connected:

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

If it doesn't work

  • Codex reads ~/.codex/config.toml. A project .codex/config.toml is only read in projects you have trusted.
  • Codex doesn't expand ~ or environment variables in command. Use a full path in the config file.
  • Servers that need a sign-in: run codex mcp login <name>.