Github Github MCP Server

Github github mcp server connects Github Github to AI assistants that speak the Model Context Protocol. 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 and tools.

What Github Github does

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 and tools.

Tools it exposes

Once connected, the assistant can call these 14 tools directly:

• Toolset — Description
• actions — GitHub Actions workflows and CI/CD operations
• 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 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

Installing the github github mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply 5 environment variables: GITHUB_PERSONAL_ACCESS_TOKEN, GITHUB_HOST, TOOL_ADD_ISSUE_COMMENT_DESCRIPTION, TOOL_CREATE_BRANCH_DESCRIPTION, YOUR_TOKEN. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

1. An MCP host that supports the latest MCP specification and remote servers, such as VS Code.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Github Github sits in that group, and the shape of its toolset — Toolset, actions, context among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This is a hosted server — you point your client at an endpoint rather than running a local process, so there is nothing to keep updated on your machine.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• With 14 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use Github Github.
• Maintained by lucascampuddu, written in Go.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the github github mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.