About Zed MCP Server Github
Zed MCP Server Github is an MCP server published by LoamStudios in the Developer Tools category: a GitHub MCP Server extension for Zed.
The repository has 94 stars and 25 forks, with the last commit 17 days ago. Recent commit activity is the strongest signal that reported issues will get attention.
Install
git clone https://github.com/LoamStudios/zed-mcp-server-githubThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about Zed MCP Server Github
Powered by Claude · Grounded in docs
Security checks
Static checks derived from the repository 17 hours ago. Heuristics on the source, not an audit.
- ✓README presentThe repository ships documentation.
- ✓License declaredUsable under a stated license.
- !Tests presentNo tests found. Behaviour changes may go unnoticed between versions.
- ✓Dependencies pinnedA lockfile pins dependency versions.
- ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
- !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.
Releases
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.
| Setting | Description |
|---|---|
github_personal_access_token |
Token to use instead of OAuth. |
github_host |
GitHub Enterprise Server or ghe.com host, e.g. https://github.example.com. |
read_only |
true to only expose read-only tools. |
toolsets |
Toolsets to enable, e.g. ["repos", "issues", "pull_requests"]. See the list of toolsets. |
README fetched from the repository 17 hours ago. The original is authoritative.