GitHub Enterprise MCP Server

GitHub Enterprise MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. github-enterprise-mcp.

What you get

An MCP (Model Context Protocol) server for integration with GitHub Enterprise API. This server provides an MCP interface to easily access repository information, issues, PRs, and more from GitHub Enterprise in Cursor.

• Retrieve repository list from GitHub Enterprise instances
• Get detailed repository information
• List repository branches
• View file and directory contents
• Manage issues and pull requests
• Repository management (create, update, delete)

What the assistant can call

Once GitHub Enterprise is connected, these are the calls the assistant has available:

• User — friendly response formatting and messages
• list-repositories — Retrieve repository list for a user or organization
• get-repository — Get detailed repository information
• list-branches — List branches of a repository
• get-content — Retrieve file or directory contents
• list-pull-requests — List pull requests in a repository
• get-pull-request — Get pull request details
• create-pull-request — Create a new pull request
• merge-pull-request — Merge a pull request
• list-issues — List issues in a repository
• get-issue — Get issue details
• list-issue-comments — List comments on an issue or pull request

Setting it up

@ddukbg/github-enterprise-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration and credentials

You will need 5 environment variables: GITHUB_ENTERPRISE_URL, GITHUB_TOKEN, LANGUAGE, YOUR_GITHUB_TOKEN, YOUR_GITHUB_ENTERPRISE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js 18 or higher - Access to a GitHub Enterprise instance - Personal Access Token (PAT)

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. GitHub Enterprise's toolset — User, list-repositories, get-repository and 11 more — is a fair guide to whether it matches your workflow. It is maintained by containerelic; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch GitHub Enterprise.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the github enterprise mcp server does with a few real requests.