Ghcli Connector MCP server

🔌 ghcli-mcp-connector

Talk to the GitHub CLI (gh) from an MCP-speaking agent.

A single static Go binary that speaks the Model Context Protocol and lets an agent run GitHub CLI commands: any gh invocation — repo, issue, pr, release, gist, workflow, run, secret, variable, project, ruleset, codespace, extension, api, and more — with a read-only-by-default safety gate on anything that changes state on GitHub.

No Python, no uv, no runtime dependency to install — just a binary and an .mcp.json. It shells out to the gh binary already installed and authenticated on the host (gh auth login, stored in the OS keychain, or GHTOKEN/GITHUBTOKEN) instead of reimplementing a GitHub API client, so it gets the full breadth of the CLI for free rather than a hand-curated subset of endpoints.

Note: this is a sibling of github-mcp-connector,

not a replacement. That one talks to the GitHub REST API directly via

google/go-github with a curated set of 18 tools. This one shells out to

the gh CLI itself — same trade-off as aws-mcp-connector vs. a

hand-written AWS SDK client: broader coverage (gh extensions, gh's own

filters/formatting, workflow/run/codespace/project/ruleset management)

through a single ghcli_exec escape hatch, instead of a curated surface.

✨ Why this exists

An agent that only has a narrow, hand-picked set of GitHub tools hits a

wall the moment you need something outside that set. This connector

instead wraps the gh CLI itself, so an agent can run gh pr list,

gh issue create, gh workflow run, gh api repos/owner/repo/issues —

anything the CLI can do — without waiting on a new tool to be written

for it. State-changing commands are blocked by default and require both

a server-level opt-in and a per-call confirm=true, so exploring/

reading is safe out of the box.

🧰 Tools

Shortened. The full README is on GitHub.