mcpField
G
GitHub MCP Server Extension for Zed

GitHub MCP Server Extension for Zed

Local
github.com/LoamStudiosVersion Control94Updated 4w ago

About GitHub MCP Server Extension for Zed

An extension that connects the GitHub MCP Server to Zed's Agent Panel as a context server. It suits Zed users who want GitHub tools in their agent workflow, with OAuth or personal access token authentication.

Key features

  1. 01Adds GitHub MCP Server to Zed Agent Panel
  2. 02OAuth login or personal access token authentication
  3. 03Supports GitHub Enterprise Server and ghe.com hosts
  4. 04Optional read-only mode for tools
  5. 05Configurable toolsets

Use cases

  1. 01Querying repositories and issues from Zed's agent
  2. 02Using GitHub Enterprise Server with an MCP server
  3. 03Restricting agent access to read-only GitHub tools

MCP support

The extension configures Zed as a client that launches and connects to the GitHub MCP Server, managing authentication, host, read-only mode and toolsets through Zed settings.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

GitHub MCP Server Extension for Zed

This extension integrates GitHub MCP Server as a context server for Zed's Agent Panel.

To install navigate to: Zed > Extensions. Or use the command palette (macOS, Linux) to search extensions.

Authentication

OAuth (default). On github.com no setup is needed. On the first tool call, the server opens your browser to log in. The token is kept in memory only, so you'll log in again after Zed restarts. If you take longer than Zed's request timeout (context_server_timeout, 60 seconds by default) to approve, the first request fails; retry it once you've approved.

Personal access token. Create a fine-grained token (or a classic token with repo scope). A token is required for GitHub Enterprise Server and ghe.com. Either export it from your shell profile, which keeps it out of Zed's settings:

export GITHUB_PERSONAL_ACCESS_TOKEN="<GITHUB_PERSONAL_ACCESS_TOKEN>"

Zed loads your login shell's environment at startup and passes it to the server, so restart Zed after changing it. GITHUB_HOST, GITHUB_READ_ONLY, and GITHUB_TOOLSETS work the same way. Values in Zed's settings take precedence over the environment.

Or add it to your settings:

"context_servers": {
  "mcp-server-github": {
    "settings": {
      "github_personal_access_token": "<GITHUB_PERSONAL_ACCESS_TOKEN>"
    }
  }
},

Settings

All settings are optional.

SettingDescription
github_personal_access_tokenToken to use instead of OAuth.
github_hostGitHub Enterprise Server or ghe.com host, e.g. https://github.example.com.
read_onlytrue to only expose read-only tools.
toolsetsToolsets to enable, e.g. ["repos", "issues", "pull_requests"]. See the list of toolsets.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.