GitHub MCP Server

This entry points at the GitHub server in the archived reference collection of the Model Context Protocol project, the TypeScript implementation that shipped alongside the protocol's first wave of examples. Status matters here: that reference server is archived, and GitHub took over with its own maintained implementation in a separate repository, which is what most teams install. The archived code remains a readable example of how a large REST API gets wrapped as MCP tools. What the reference version exposed maps closely to everyday repository work: creating and updating files, pushing several files in one commit, creating repositories, forking them, and creating branches, opening and commenting on issues, and creating and updating pull requests. Search tools cover code, issues, and users, which is what lets an agent locate the file or the prior discussion it needs before touching anything. Everything runs under a personal access token, so the token's scopes are the real boundary on what an agent can reach and modify. If you are choosing a GitHub server rather than studying one, prefer the maintained implementation. It covers considerably more of the API, including workflow runs, releases, code scanning, and notifications, and offers a hosted remote option alongside the local process. Use this archived entry to understand the lineage of GitHub tooling in MCP, not as the server to deploy into a working setup.