GitHub Enterprise MCP Server with support for repository operations
Github MCP server exists for a simple reason — assistants are far more useful when they can act on Github directly instead of describing what you should do. GitHub Enterprise MCP Server with support for repository operations.
An MCP server for GitHub Enterprise that handles repository access, branch creation, commits, and pushes.
Once Github is connected, these are the calls the assistant has available:
test-api-connection — Test connection to a GitHub API endpointconnect-github-enterprise — Connect to a GitHub Enterprise instanceGitHub.com — Use https://github.com or https://api.github.comconnect-github-enterprise-2fa — Connect to a GitHub Enterprise instance with 2FAlist-repositories — List repositories from the connected GitHub Enterprise instancecreate-branch — Create a new branch in a repositorycommit-and-push — Commit file changes and push to a branchResources — The server implements GitHub Enterprise repositories as resources: - Custom github:// URI scheme for accessing repositories - Each repositoryPrompts — The server provides the following prompts: - repo-details: Gets detailed information about a repository - Required "repository" argument to specifyTools — The server implements the following tools: - test-api-connection: Test connection to a GitHub API endpoint - Takes "url" as a required stringDebugging — Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the [MCPThe server ships on npm as @modelcontextprotocol/inspector, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
You will need 4 environment variables: GITHUB_CONNECTION_NAME, GITHUB_URL, GITHUB_TOKEN, UV_PUBLISH_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.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Github's toolset — test-api-connection, connect-github-enterprise, GitHub.com and 8 more — is a fair guide to whether it matches your workflow. It is maintained by akhilthomas236; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Github's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| test-api-connection | Test connection to a GitHub API endpoint |
| connect-github-enterprise | Connect to a GitHub Enterprise instance |
| GitHub.com | Use https://github.com or https://api.github.com |
| connect-github-enterprise-2fa | Connect to a GitHub Enterprise instance with 2FA |
| list-repositories | List repositories from the connected GitHub Enterprise instance |
| create-branch | Create a new branch in a repository |
| commit-and-push | Commit file changes and push to a branch |
| Resources | The server implements GitHub Enterprise repositories as resources: - Custom github:// URI scheme for accessing repositories - Each repository resource has a name, description and custom mimetype - Resources are dynamical |
| Prompts | The server provides the following prompts: - repo-details: Gets detailed information about a repository - Required "repository" argument to specify the repository - Returns comprehensive information about the repository |
| Tools | The server implements the following tools: - test-api-connection: Test connection to a GitHub API endpoint - Takes "url" as a required string argument - Tests multiple API endpoint formats to determine which works - Prov |
| Debugging | Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector). |
"mcpServers": {
"github-enterprise-mcp": {
"command": "uv",
"args": [
"--directory",
"/Users/annmariyajoshy/vibecoding/github-enterprise-mcp",
"run",
"github-enterprise-mcp"
]
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| GITHUB_CONNECTION_NAME | Configuration value read at startup. | Optional |
| GITHUB_URL | Endpoint or connection string the server talks to. | Yes |
| GITHUB_TOKEN | Credential the server authenticates with. | Yes |
| UV_PUBLISH_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.