MCPSTACK

Field reports on MCP servers — dev & devops · est. 2026

SEED LISTING — drafted before hands-on verification. Re-test before this case file is considered final.

GitHub MCP Server (official)

Use it

Source control / CI · last verified 2026-07-29

VendorGitHub (official)
Repo / hostgithub/github-mcp-server
PricingFree (GitHub plan limits apply)
AuthPAT or OAuth
TransportLocal (Docker/binary) or GitHub-hosted remote
setup4/5
reliability5/5
capability4/5
maintenance5/5
trust4/5

What it does

Exposes repositories, issues, pull requests, code search and Actions runs as agent tools. The official server replaced most community GitHub wrappers during 2025 — it is the default choice for wiring an agent into your GitHub org.

The short verdict

Being first-party matters here: auth is handled properly (fine-grained PATs work), the toolset tracks the real API, and maintenance is not a question mark. The main friction is tool count — it exposes a lot, so scope your agent’s allowed tools or the model wastes context choosing.

Use it if: your agent touches GitHub at all.

Skip if: you only need read-only public repo access — plain HTTP fetch may be enough.

Reviewed on MCPstack? Add the badge

Reviewed on MCPstack: GitHub MCP Server (official)
[![Reviewed on MCPstack](https://mcpstack.dev/badge.svg)](https://mcpstack.dev/listings/github-mcp-server)