Log inSubmit server
Github Enterprise MCP logo

Github Enterprise MCP

by ddukbg

Connects AI clients to GitHub Enterprise for repository, issue, pull request, workflow, and enterprise administration tasks.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Github Enterprise MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "ddukbg-github-enterprise-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@ddukbg/github-enterprise-mcp"
      ],
      "env": {
        "GITHUB_TOKEN": "YOUR_VALUE_HERE",
        "GITHUB_ENTERPRISE_URL": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @ddukbg/github-enterprise-mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

The ddukbg/github-enterprise-mcp MCP server exposes GitHub Enterprise API operations as MCP tools for repository, branch, content, issue, pull request, workflow, and enterprise information. It authenticates with a GitHub personal access token and targets a configurable GitHub Enterprise API URL, with support for GitHub.com and GitHub Enterprise Cloud for most general operations. Run it locally with Node.js or Docker, using HTTP/SSE or a client command configuration. Reach for it when an agent needs to inspect or modify GitHub repositories and automation without a custom API wrapper.

Use cases

  • Inspect repositories, branches, and file contents
  • Create and merge pull requests
  • Track and create repository issues
  • Trigger workflows and review workflow runs
  • Query GitHub Enterprise license and system statistics

Key features

  • Repository listing and administration
  • Branch and file content retrieval
  • Issue and pull request management
  • GitHub Actions workflow operations
  • Enterprise license and statistics queries

Tools20

What Github Enterprise MCP lets your agent do. Expand a tool for its parameters.

Self-reported~220 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

19/19 checks healthy over the last 80d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · @ddukbg/github-enterprise-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars29Stargazers on the source repository.
npm downloads101Package downloads in the last 30 days.
Last commit1y agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed20Callable tools this server registers over MCP.
Directory activity6 viewsConfig copies, upvotes, and views on AllMCPs.

How Github Enterprise MCP works

What ddukbg/github-enterprise-mcp MCP server does

The ddukbg/github-enterprise-mcp MCP server presents selected GitHub Enterprise API operations through the Model Context Protocol. It covers repository discovery and administration, branch listing, file and directory retrieval, issue management, pull request workflows, GitHub Actions workflows and runs, and enterprise-level license and statistics queries.

The repository is primarily intended for GitHub Enterprise Server deployments.

How it works

The server uses a GitHub personal access token together with the base URL of the target GitHub Enterprise API. For a self-hosted GitHub Enterprise Server instance, the URL typically points to an API path such as https://github.example.com/api/v3. Requests made through MCP are translated into GitHub API calls, and responses are formatted for client use.

It supports HTTP transport, including an SSE endpoint used by the documented Cursor configuration. Node.js 18 or later is listed as a prerequisite for local operation, and Docker is supported as an alternative runtime.

Setup and configuration

Set GITHUB_TOKEN to a personal access token and GITHUB_ENTERPRISE_URL to the target API URL. The token must have permissions appropriate to the operation; repository tools in the documented table require the repo permission. The server can also receive the token and URL through command-line options in HTTP mode.

For local development, clone the repository, install its npm dependencies, and run the development script. For a production-style local setup, build the project and start dist/index.js with HTTP transport. Docker users can build the included image and pass the same environment variables when starting the container. DEBUG enables debug logging, while LANGUAGE or the corresponding command-line option selects English or Korean output; English is the default.

Tools and capabilities

The documented MCP tool set includes:

  • List repositories for a user or organization, with filtering, sorting, and pagination.
  • Retrieve repository details, branches, and file or directory contents.
  • List, inspect, create, and merge pull requests.
  • List, inspect, comment on, and create issues.
  • Create, update, or delete repositories.
  • List GitHub Actions workflows, inspect workflow runs, and trigger workflows.
  • Retrieve GitHub Enterprise license information and system statistics.

These write operations can change repositories or trigger automation, so client users should review the token permissions and the requested action before allowing an agent to run them.

Limitations and notes

The ddukbg/github-enterprise-mcp MCP server does not provide the enterprise-only license and statistics features when connected to GitHub.com or GitHub Enterprise Cloud. The available operations also depend on the permissions granted to the personal access token. The README recommends URL mode for Cursor and describes command mode as an alternative.

It does not establish a confirmed published package or a universal one-command installation path.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Github Enterprise MCP

Clone the repository, install dependencies with npm, and build or run the project locally. Docker setup is also documented.

Yes. The README provides a Claude Desktop configuration using a command-based MCP setup and the package name shown in its example.

Yes. Cursor is the primary client mentioned in the README. URL mode using the local SSE endpoint is recommended, and command mode is also described.

It requires a GitHub personal access token and the GitHub Enterprise API URL. Repository operations documented in the README require the token to have the repo permission.

Related MCP servers

All in Version Control All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewGithub Enterprise MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/ddukbg-github-enterprise-mcp?style=directory)](https://allmcps.com/mcp/ddukbg-github-enterprise-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/ddukbg-github-enterprise-mcp"><img src="https://allmcps.com/api/badge/ddukbg-github-enterprise-mcp?style=directory" alt="Github Enterprise MCP on AllMCPs" /></a>