GitHub Enterprise MCP Server

What is GitHub Enterprise MCP Server?

An MCP server that integrates with the GitHub Enterprise API, providing an MCP interface to access repository information, issues, pull requests, and more from GitHub Enterprise in Cursor. It is designed for GitHub Enterprise Server but also works with GitHub.com and GitHub Enterprise Cloud.

How to use GitHub Enterprise MCP Server?

Install via Docker or clone the repository, set environment variables GITHUB_TOKEN and GITHUB_ENTERPRISE_URL, then run with npm run dev for development or node dist/index.js --transport http for production. Connect to Cursor using URL mode (http://localhost:3000/sse) or command mode with npx @ddukbg/github-enterprise-mcp.

Key features of GitHub Enterprise MCP Server

• Retrieve and manage repositories, branches, files, issues, and PRs
• Manage GitHub Actions workflows and users
• Create, update, and delete repositories
• Access enterprise statistics and license information
• Enhanced error handling and user-friendly response formatting
• Supports both English and Korean languages

Use cases of GitHub Enterprise MCP Server

• Automate repository and issue management inside Cursor via MCP
• Integrate GitHub Enterprise API access into AI coding assistants
• Manage pull requests and workflows without leaving the editor
• Enforce repository settings across an organization

FAQ from GitHub Enterprise MCP Server

Does it work with GitHub.com or GitHub Enterprise Cloud?

Yes, it works with GitHub.com and GitHub Enterprise Cloud, but some enterprise-specific features like license information and enterprise statistics will not function.

What are the prerequisites?

Node.js 18 or higher, access to a GitHub Enterprise instance, and a personal access token (PAT) with appropriate permissions.

How do I configure languages?

Set the LANGUAGE environment variable to ko for Korean or use the --language ko command-line argument. The default is English.

What transport modes are supported?

The server supports HTTP mode with SSE endpoint (http://localhost:3000/sse) by default. It can also run in stdio mode for command-line integration.

What permissions does the PAT need?

Required permissions vary by tool; common scopes include repo, delete_repo, and actions:read. Refer to the tool table in the README for each operation.