GitHub

Omnigit GitHub & Local Git MCP Server

The Omnigit GitHub & Local Git MCP Server connects AI tools directly to GitHub's platform. This gives AI agents, assistants, and chatbots the ability to read repositories and code files, manage issues and PRs, analyze code, and automate workflows. All through natural language interactions.

Use Cases

• Repository Management: Browse and query code, search files, analyze commits, and understand project structure across any repository you have access to.
• Issue & PR Automation: Create, update, and manage issues and pull requests. Let AI help triage bugs, review code changes, and maintain project boards.
• CI/CD & Workflow Intelligence: Monitor GitHub Actions workflow runs, analyze build failures, manage releases, and get insights into your development pipeline.
• Code Analysis: Examine security findings, review Dependabot alerts, understand code patterns, and get comprehensive insights into your codebase.
• Team Collaboration: Access discussions, manage notifications, analyze team activity, and streamline processes for your team.

Built for developers who want to connect their AI tools to GitHub context and capabilities, from simple natural language queries to complex multi-step agent workflows.

---

Fork differences from upstream

This is a fork of github/github-mcp-server with the following additions and improvements.

For the maintained backport checklist, see Fork Differences From Upstream.

Improved review comment ID resolution

get_review_comments now returns a CommentID field (which is the databaseId from GraphQL) alongside the GraphQL NodeID and DatabaseID for every comment node. This CommentID is the numeric ID that should be used when calling add_reply_to_pull_request_comment or pull_request_comment_write. Previously, only the opaque base64 GraphQL node ID was returned, forcing the model to decode it or scrape the numeric ID from comment URLs. The commentId / comment_id parameter descriptions in those tools now explicitly say to use the CommentID field.

Issue comment management (issue_comment_write)

A new issue_comment_write tool lets AI agents update or delete existing issue comments. Previously only add_issue_comment (create) was available.

PR review comment management (pull_request_comment_write)

A new pull_request_comment_write tool lets AI agents update or delete existing pull request review comments.

Body filtering (filter_patterns)

Issue bodies, PR bodies, and local git commit messages are filtered before being sent to GitHub. By default, Co-Authored-By: trailers and generic AI-generated PR footers are stripped. The filter list is fully configurable via filter_patterns in omnigit-mcp-config.json. See i18n / Overriding Descriptions for details.

Local Git toolset (local_git)

A full set of git_* tools for operating on local repositories without going through the GitHub API: git_add, git_apply_patch_file, git_apply_patch_string, git_checkout, git_commit, git_create_branch, git_diff, git_diff_staged, git_diff_unstaged, git_init, git_list_repositories, git_log, git_pull, git_push, git_reset, git_show, and git_status.

---

Remote GitHub MCP Server

The remote GitHub MCP Server is hosted by GitHub and provides the easiest method for getting up and running. If your MCP host does not support remote MCP servers, don't worry! You can use the local version of the GitHub MCP Server instead.

Prerequisites

1. A compatible MCP host with remote server support (VS Code 1.101+, Claude Desktop, Cursor, Windsurf, etc.)
2. Any applicable policies enabled

Install in VS Code

For quick installation, use one of the one-click install buttons above. Once you complete that flow, toggle Agent mode (located by the Copilot Chat text input) and the server will start. Make sure you're using VS Code 1.101 or later for remote MCP and OAuth support.

Alternatively, to manually configure VS Code, choose the appropriate JSON block from the examples below and add it to your host configuration:

Using OAuth Using a GitHub PAT VS Code (version 1.101 or greater)

{

"servers": { "github": { "type": "http", "url": "https://api.githubcopilot.com/mcp/" } } }

{

"servers": { "github": { "type": "http", "url": "https://api.githubcopilot.com/mcp/", "headers": { "Authorization": "Bearer ${input:github_mcp_pat}" } } }, "inputs": [ { "type": "promptString", "id": "github_mcp_pat", "description": "GitHub Personal Access Token", "password": true } ] }

Install in other MCP hosts

• [Copilot CLI](/docs/installation-guides/install-copilot-cli.md) - Installation guide for GitHub Copilot CLI
• [GitHub Copilot in other IDEs](/docs/installation-guides/install-other-copilot-ides.md) - Installation for JetBrains, Visual Studio, Eclipse, and Xcode with GitHub Copilot
• [Claude Applications](/docs/installation-guides/install-claude.md) - Installation guide for Claude Desktop and Claude Code CLI
• [Codex](/docs/installation-guides/install-codex.md) - Installation guide for OpenAI Codex
• [Cursor](/docs/installation-guides/install-cursor.md) - Installation guide for Cursor IDE
• [OpenCode](/docs/installation-guides/install-opencode.md) - Installation guide for the OpenCode terminal agent
• [Windsurf](/docs/installation-guides/install-windsurf.md) - Installation guide for Windsurf IDE
• [Zed](/docs/installation-guides/install-zed.md) - Installation guide for Zed editor
• [Rovo Dev CLI](/docs/installation-guides/install-rovo-dev-cli.md) - Installation guide for Rovo Dev CLI

Note: Each MCP host application needs to configure a GitHub App or OAuth App to support remote access via OAuth. Any host application that supports remote MCP servers should support the remote GitHub server with PAT authentication. Configuration details and support levels vary by host. Make sure to refer to the host application's documentation for more info.

Configuration

Toolset configuration

See Remote Server Documentation for full details on remote server configuration, toolsets, headers, and advanced usage. This file provides comprehensive instructions and examples for connecting, customizing, and installing the remote GitHub MCP Server in VS Code and other MCP hosts.

When no toolsets are specified, default toolsets are used.

Insiders Mode

Try new features early! The remote server offers an insiders version with early access to new features and experimental tools.

Using URL Path Using Header

{

"servers": { "github": { "type": "http", "url": "https://api.githubcopilot.com/mcp/insiders" } } }

{

"servers": { "github": { "type": "http", "url": "https://api.githubcopilot.com/mcp/", "headers": { "X-MCP-Insiders": "true" } } } }

See Remote Server Documentation for more details and examples, and Insiders Features for a full list of what's available.

GitHub Enterprise

GitHub Enterprise Cloud with data residency (ghe.com)

GitHub Enterprise Cloud can also make use of the remote server.

Example for https://octocorp.ghe.com with GitHub PAT token:

{

... "github-octocorp": { "type": "http", "url": "https://copilot-api.octocorp.ghe.com/mcp", "headers": { "Authorization": "Bearer ${input:github_mcp_pat}" } }, ... }

Note: When using OAuth with GitHub Enterprise with VS Code and GitHub Copilot, you also need to configure your VS Code settings to point to your GitHub Enterprise instance - see Authenticate from VS Code

GitHub Enterprise Server

GitHub Enterprise Server does not support remote server hosting. Please refer to GitHub Enterprise Server and Enterprise Cloud with data residency (ghe.com) from the local server configuration.

---

Local GitHub MCP Server

Prerequisites

1. To run the server in a container, you will need to have Docker installed.
2. Once Docker is installed, you will also need to ensure Docker is running. The Docker image is available at ghcr.io/aifity/omnigit-mcp. The image is public; if you get errors on pull, you may have an expired token and need to docker logout ghcr.io.
3. Authentication. On github.com you don't need to create anything up fro