[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f3paw9l87e9wld":3},{"code":4,"message":5,"data":6,"timestamp":41},10000,"success",{"full_name":7,"position":8,"description":9,"language":10,"stars":11,"forks":12,"stars_gained":13,"age_days":14,"hn_threads":15,"one_liner":28,"summary_md":29,"topic":30,"github_topics":33,"license":37,"homepage":38,"updated_at":39,"history":40},"github\u002Fgithub-mcp-server",11,"GitHub's official MCP Server","Go",33925,5224,257,599,[16,22],{"id":17,"title":18,"points":19,"comments":20,"posted_at":21},43611875,"GitHub's Official MCP Server",6,0,"2025-04-07",{"id":23,"title":24,"points":25,"comments":26,"posted_at":27},43587130,"GitHub MCP Server",5,2,"2025-04-04","Connects AI coding agents to GitHub repositories, issues, PRs and Actions through the Model Context Protocol.","## The problem\n\nAI coding assistants are now good at reading and writing code inside a single working copy, but they go blind the moment a task crosses into GitHub: searching across other repositories, reading a failed Actions run, triaging an issue queue, or checking Dependabot alerts. The usual workarounds are pasting links, copying API output into the chat, or writing ad-hoc scripts with the REST API. Each works, none composes, and every agent ends up with its own inconsistent GitHub glue. This project exposes GitHub as an MCP server so any MCP-capable host can call the same set of operations.\n\n## What's different\n\nMost MCP servers for GitHub in circulation are community wrappers around the REST API, built quickly and scoped to whichever endpoints their authors needed. The difference here is provenance and hosting. It is the official server from GitHub, it can run as a hosted remote endpoint with OAuth, so there is no container or binary to manage, and it offers a local\u002FDocker alternative plus a GitHub Enterprise path, including data-residency domains. It also ships an insiders mode with experimental tools, and a toolset configuration that lets you trim which capabilities an agent can reach rather than exposing everything.\n\nAgainst hand-rolled REST scripts, the gain is a standard protocol and a stable tool surface that any host speaks; the loss is flexibility, since you work within the tools GitHub exposes and cannot invent endpoints casually. Against general-purpose code hosts' agents-in-the-loop, this keeps GitHub's own data model as the source of truth.\n\n## Who it's for\n\nDevelopers already running an MCP-capable host (VS Code with Copilot, Claude Code, Cursor, Codex, Zed, Windsurf) who want their agent to act on GitHub rather than just local files. Platform teams maintaining internal agents benefit from OAuth plus Enterprise support and the ability to restrict toolsets. Teams on GitHub Enterprise Server should note that remote hosting is unavailable there and must use the local server. Anyone wanting deep, custom GitHub automation outside an LLM loop is better served by the REST\u002FGraphQL APIs and `gh` directly; MCP is a layer for models, not a scripting interface.\n\n## Cost of adoption\n\nYou need a compatible host; remote access via OAuth requires the host to support OAuth (VS Code 1.101+), otherwise a PAT works. A GitHub token with the right scopes is the main risk surface, since an agent with write access to issues and PRs can act on your behalf; scoping token permissions and toolsets is essential. The Go module path is in flux: the README states the existing `v2.0.0` tag predates a module-path correction and cannot be used as a Go module, so library consumers are stuck on pseudo-versions until a new tag lands. The README is detailed on installation but says little about rate limits, tool-level permissions and failure modes, so expect to read the docs folder.\n\n## Verdict\n\nThe repository is about 599 days old with roughly 33.9k stars, so the star count reflects a burst of attention rather than years of accumulation; it is young by infrastructure standards. Interest is not fading: it gained 258 stars on the weekly Go board and ranked #11 as of 2026-10-24, though it has never appeared on the daily board. Hacker News attention is thin, with a single 6-point thread, so the buzz is concentrated in developer tooling circles rather than broad. For most teams using an MCP host, this is the default choice precisely because it is official and hosted; just pin your token scopes and treat the Go API as unstable for now.",{"slug":31,"name":32},"developer-tools","Developer Tools",[34,35,36],"github","mcp","mcp-server","MIT",null,"2026-10-24T23:36:38Z",[],1792901725]