Connect GitHub MCP to Zed
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
- Zed 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_TOKENin your environment. To skip Docker, use GitHub MCP (remote), the hosted version.
Step 1: Add GitHub MCP 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": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "GITHUB_PERSONAL_ACCESS_TOKEN", "ghcr.io/github/github-mcp-server" ], "env": { "GITHUB_PERSONAL_ACCESS_TOKEN": "YOUR_GITHUB_PERSONAL_ACCESS_TOKEN" } } } }Good to know- Zed keeps environment values in your settings file, which stays on your machine. Replace each
YOUR_…placeholder with the real value.
- Zed keeps environment values in your settings file, which stays on your machine. Replace each
Step 2: Check it's connected
Open Settings → AI → MCP Servers. A green dot next to the server means it is running.
Step 3: Try a first request
Ask Zed something that only works with GitHub MCP connected:
Say to Zed List the open pull requests in this repository and summarise what the newest one changes.
If it doesn't work
- Zed reads MCP servers from the
context_serverskey, notmcpServers. 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_permissionsin your settings.





