Refined MCP server for GitHub

If you haven't read the article The second wave of MCP: Building for LLMs, not developers by Vercel, I highly recommend checking it out to understand why we're building this project.

GitHub's official MCP Server exposes dozens of low-level tools that bloat token usage and are mostly impractical for LLMs. gh-mcp achieves the best of both worlds by providing powerful interfaces: GitHub GraphQL and Code Search, wrapped with smart abstractions.

This project does 3 things differently:

Powerful interfaces — exposes GraphQL and Code Search instead of atomized endpoints. LLMs already understand these APIs.
YAML output — makes nested data and file content readable without escaping.
Clean abstractions — gh handles authentication and low-level details. And LLMs know how to use its --jq option to filter.

Swapping in gh-mcp delivers better performance at lower cost for any GitHub interactions.

Installation

with uv:

uvx mcp-hmr

MCP config:

{
    "mcpServers": {
        "gh": {
            "command": "uvx",
            "args": ["gh-mcp"]
        }
    }
}

If you prefer serving it via streamable-http:

uvx gh-mcp --http

This project requires gh CLI to be installed and authenticated. Please follow the instructions at cli.github.com to set it up. And then you can login via gh auth login. Check that gh auth status works before using this MCP server.

Metadata

Release files for gh-mcp 0.3.8

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for gh-mcp 0.3.8
File	Interpreter	ABI	Platform	Reset
gh_mcp-0.3.8-py3-none-any.whl 9.9 kB Aug 28, 2026	Python 3	none	any	Details

Release files / gh_mcp-0.3.8-py3-none-any.whl

Download URL	gh_mcp-0.3.8-py3-none-any.whl
Size	9.9 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`1b0de205c358e56a2464611d4a736e64810059044c3f6a0b8107b5bcb76f6b5d`
BLAKE2b-256 checksum How to use checksums	`6fc6ddd6f1b12118ae0535f87d83b5c32e025ffdf2e4cfe95cf114736fb1852b`
Upload date	Aug 28, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/promplate/refined-mcp-servers
Publishing commit: github.com/promplate/refined-mcp-servers/tree/b7abbcfe7e4f5fd08e25ca503a3a7238b8a29d4a

Workflow

Publishing configuration: github.com/promplate/refined-mcp-servers/blob/b7abbcfe7e4f5fd08e25ca503a3a7238b8a29d4a/.github/workflows/ci.yml
Publishing logs: github.com/promplate/refined-mcp-servers/actions/runs/33213145386/attempts/1

Artifact

Subject: gh_mcp-0.3.8-py3-none-any.whl
SHA-256 checksum: 1b0de205c358e56a2464611d4a736e64810059044c3f6a0b8107b5bcb76f6b5d Verifying attestations