JohnXu22786/github-mcp

GitHub workbench MCP server (dsh bundle): 23 MCP tools for repos, issues, PRs, code review, and search, with zero runtime dependencies and PAT/OAuth auth.

repogate is a GitHub workbench for coding agents: it wraps the GitHub REST API into MCP tools so an agent can browse repos, manage issues, create and merge PRs, review code and search — directly in a conversation. Installed as a dsh bundle, its repogate/bridge plugin launches the MCP server inside the dsh process and registers the tools into ctx.tools as mcprepogate* with no manual config. It documents dual auth (personal access token or OAuth device flow with local token caching), a read-only mode that blocks all write operations, rate-limit/permission errors that carry a fix guide, and slim list/search output to save context.

Tools & Capabilities ★ 1 updated 2026-08-17
View on GitHub ↗

Install

dsh plugin --profile demo add github:JohnXu22786/github-mcp

README "Installing in DSH" block quoted verbatim. The README also documents installing it from a local checkout with dsh plugin --profile web add ., and an uninstall of dsh plugin --profile web remove repogate. The registry carries no published package for repogate (the README's zero-runtime-dependency claim is about Node built-ins, not an npm package), so no npm version is asserted.

Compatibility

README: works with any MCP-capable client, ships a dsh bundle (cordis.patch.yml + a bridge plugin) for one-step dsh plugin add, zero runtime dependencies, and needs a GitHub token via REPOGATE_TOKEN or GITHUB_TOKEN. The README notes dsh does not enable any MCP server by default and that a bundle line is the enable action, so only trusted plugins should be installed.

Details

Recent updates

The README documents the tool set, install paths and auth model rather than a release-by-release table.

FAQ

How do I install it for dsh?
The README's DSH install command is dsh plugin --profile demo add github:JohnXu22786/github-mcp; a local checkout can be added with dsh plugin --profile web add ..
How does it authenticate to GitHub?
The README documents two channels — a personal access token and an OAuth device-authorization flow — with local token caching; the token is inherited from the dsh process environment by default.
Can I prevent it from writing to GitHub?
Yes — the README documents a read-only mode that blocks all write operations with one switch.

More plugins in Tools & Capabilities

Browse more in Tools & Capabilities

Guides for Tools & Capabilities plugins