MCP Server for the GitHub Enterprise APIs, enabling file operations, repository management, search functionality, and more.
MCP Server for the GitHub Enterprise APIs, enabling file operations, repository management, search functionality, and more. The github enterprise mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 5 defined tools rather than through you.
Everything the assistant can do here goes through one of these:
Inputs — - owner (string): Repository owner (username or organization)Returns — File content and commit detailsPrerequisites — 1. Node.js installed on your system 2. A GitHub Personal Access Token with appropriate permissions 3. Cline installed on your systemVerification — To verify that the GitHub Enterprise MCP server is properly installed and configured, you can ask Cline to use one of the GitHub tools:Troubleshooting — If you encounter issues with the GitHub Enterprise MCP server:You will need 4 environment variables: GITHUB_PERSONAL_ACCESS_TOKEN, GITHUB_API_URL, GITHUB_API_VERSION, YOUR_TOKEN. 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.
Installation goes through your MCP client rather than a global install: point it at npm on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. GitHub Enterprise's toolset — Inputs, Returns, Prerequisites and 2 more — is a fair guide to whether it matches your workflow. It is maintained by piyushgIITian; 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.
| Tool | What it does |
|---|---|
| Inputs | - owner (string): Repository owner (username or organization) |
| Returns | File content and commit details |
| Prerequisites | 1. Node.js installed on your system 2. A GitHub Personal Access Token with appropriate permissions 3. Cline installed on your system |
| Verification | To verify that the GitHub Enterprise MCP server is properly installed and configured, you can ask Cline to use one of the GitHub tools: |
| Troubleshooting | If you encounter issues with the GitHub Enterprise MCP server: |
{
"mcpServers": {
"github": {
"command": "node",
"args": [
"/path/to/github-enterprise-mcp/dist/index.js"
],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| GITHUB_PERSONAL_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
| GITHUB_API_URL | Endpoint or connection string the server talks to. | Yes |
| GITHUB_API_VERSION | Configuration value read at startup. | Optional |
| YOUR_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.