Everything about repositories, PRs, issues and Actions works against GitHub.com and Enterprise Cloud too, so you can use it anywhere. What you cannot get elsewhere is the instance side: get-license-info, get-enterprise-stats and the create/suspend user tools. Those need a site administrator account, and the repository notes that a Classic Personal Access Token is the one to use — fine-grained tokens may not carry enterprise-level permissions.
A TypeScript server for the GitHub Enterprise API that covers repository browsing, pull requests, issues, Actions workflows and user administration, and also works against GitHub.com and Enterprise Cloud.
- Repositories: list-repositories, get-repository, list-branches, get-content for files and directories
- Pull requests: list-pull-requests, get-pull-request, create-pull-request, merge-pull-request with a choice of merge method
- Issues: list-issues, get-issue, list-issue-comments, create-issue with labels, assignees and milestone
- Repository administration: create-repository, update-repository, delete-repository behind an explicit confirmation flag
- Actions: list-workflows, list-workflow-runs filtered by branch or status, trigger-workflow with inputs
- User administration for Enterprise Server: list, get, create, update, suspend and unsuspend users, and list a user's organizations
- get-license-info and get-enterprise-stats, for instance-level licence and system statistics
- English or Korean responses, chosen with LANGUAGE or --language
A Personal Access Token in GITHUB_TOKEN and your instance API URL in GITHUB_ENTERPRISE_URL. Node.js 18 or higher; published as @ddukbg/github-enterprise-mcp and also runnable as a container over HTTP. Token scopes decide what works: repo for most tools, delete_repo for repository deletion, actions:read and actions:write for workflows.
One command plus a key — npx -y @ddukbg/github-enterprise-mcp --token=YOUR_GITHUB_TOKEN --github-enterprise-url=YOUR_GITHUB_ENTERPRISE_URL, then supply credentials