Github Enterprise MCP Server

Github enterprise mcp mcp server connects Github Enterprise MCP to AI assistants that speak the Model Context Protocol. MCP server for GitHub Enterprise API integration with Cursor, enabling AI access to repositories, issues, PRs and workflows.

What Github Enterprise MCP does

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.

Key capabilities

• 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)
• GitHub Actions workflows management
• User management (list, create, update, delete, suspend/unsuspend users)

Tools it exposes

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

• 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
• create-issue — Create a new issue
• create-repository — Create a new repository

Installing the github enterprise mcp mcp server

The server is distributed via npm as @ddukbg/github-enterprise-mcp, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

Before the server will start you need to supply 5 environment variables: GITHUB_ENTERPRISE_URL, GITHUB_TOKEN, LANGUAGE, YOUR_GITHUB_TOKEN, YOUR_GITHUB_ENTERPRISE_URL. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

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

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 Enterprise MCP sits in that group, and the shape of its toolset — User, list-repositories, get-repository 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 server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• 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 Enterprise MCP.
• Maintained by ddukbg, written in TypeScript.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the github enterprise mcp 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.