The GitHub MCP Server is a [Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction) server that provides seamless integration
The GitHub MCP Server is a Model Context Protocol (MCP) server that provides seamless integration with GitHub APIs, enabling advanced automation and interaction capabilities for developers. That is what the mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
The server publishes 13 tools. What each one is for:
Toolset — Descriptioncontext — Strongly recommended: Tools that provide context about the current user and GitHub context you are operating incode_security — Code scanning alerts and security featuresissues — Issue-related tools (create, read, update, comment)notifications — GitHub Notifications related toolspull_requests — Pull request operations (create, merge, review)repos — Repository-related tools (file operations, branches, commits)secret_protection — Secret protection related tools, such as GitHub Secret Scanningusers — Anything relating to GitHub Usersexperiments — Experimental features (not considered stable)Configuration — See Remote Server Documentation on how to pass additional configuration settings to the remote GitHub MCP ServerUsers — The Users tool exposed by this serverConfiguration is passed through the environment: GITHUB_PERSONAL_ACCESS_TOKEN, GITHUB_HOST, TOOL_ADD_ISSUE_COMMENT_DESCRIPTION, TOOL_CREATE_BRANCH_DESCRIPTION, YOUR_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP's toolset — Toolset, context, code_security and 10 more — is a fair guide to whether it matches your workflow. It is maintained by vickigogo; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Toolset | Description |
| context | **Strongly recommended**: Tools that provide context about the current user and GitHub context you are operating in |
| code_security | Code scanning alerts and security features |
| issues | Issue-related tools (create, read, update, comment) |
| notifications | GitHub Notifications related tools |
| pull_requests | Pull request operations (create, merge, review) |
| repos | Repository-related tools (file operations, branches, commits) |
| secret_protection | Secret protection related tools, such as GitHub Secret Scanning |
| users | Anything relating to GitHub Users |
| experiments | Experimental features (not considered stable) |
| Configuration | See [Remote Server Documentation](docs/remote-server.md) on how to pass additional configuration settings to the remote GitHub MCP Server. |
| Users | The Users tool exposed by this server. |
| Issues | The Issues tool exposed by this server. |
{
"mcpServers": {
"github-remote": {
"url": "https://api.githubcopilot.com/mcp/"
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| GITHUB_PERSONAL_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
| GITHUB_HOST | Endpoint or connection string the server talks to. | Optional |
| TOOL_ADD_ISSUE_COMMENT_DESCRIPTION | Configuration value read at startup. | Optional |
| TOOL_CREATE_BRANCH_DESCRIPTION | Configuration value read at startup. | Optional |
| YOUR_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.