Skip to content

Connect GitHub MCP (remote) to Zed

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

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

    Add it to your settings

    Run zed: open settings file from the command palette and add this inside the top-level object, next to your other settings.

    ~/.config/zed/settings.json
    {
      "context_servers": {
        "github-remote": {
          "url": "https://api.githubcopilot.com/mcp/",
          "headers": {
            "Authorization": "Bearer YOUR_GITHUB_PERSONAL_ACCESS_TOKEN"
          }
        }
      }
    }
    Good to know
    • Zed keeps header values in your settings file, which stays on your machine. Replace YOUR_GITHUB_PERSONAL_ACCESS_TOKEN with the token.
  2. Step 2: Check it's connected

    Open Settings → AI → MCP Servers. A green dot next to the server means it is running.

  3. Step 3: Try a first request

    Ask Zed something that only works with GitHub MCP (remote) connected:

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

If it doesn't work

  • Zed reads MCP servers from the context_servers key, not mcpServers. Servers under any other key are ignored.
  • Run zed: open settings file from the command palette to edit your settings.
  • Zed asks before running each tool. Change this with agent.tool_permissions in your settings.