GitHub Enterprise
Connect AI tools to GitHub Enterprise Server
About
Connect AI tools to GitHub Enterprise Server with a containerized MCP server. GitHub does not provide a hosted remote MCP endpoint for GitHub Enterprise Server.
Read the official GitHub Enterprise MCP server documentation.
This server is appropriate for connecting to self-hosted instances of GitHub Enterprise Server. If you’re using GitHub Enterprise Cloud with data residency (*.ghe.com), we recommend using the GitHub Enterprise Cloud MCP server. For standard GitHub Enterprise Cloud on github.com, use the regular GitHub catalog entry.
This MCP server connects AI tools directly to GitHub Enterprise Server. It gives AI agents, assistants, and chatbots the ability to read repositories and code files, manage issues and PRs, analyze code, and automate workflows through natural language interactions.
Features
- Repository Management: Browse and query code, search files, analyze commits, and understand project structure
- Issue & PR Automation: Create, update, and manage issues and pull requests with AI assistance
- CI/CD & Workflow Intelligence: Monitor GitHub Actions workflow runs, analyze build failures, and manage releases
- Code Analysis: Examine security findings, review Dependabot alerts, and understand code patterns
- Team Collaboration: Access discussions, manage notifications, and streamline team processes
- Modular Toolsets: Enable or disable specific groups of functionality via configuration
- Dynamic Tool Discovery: Turn on toolsets in response to user prompts (beta)
What you’ll need to connect
Required:
- GitHub Personal Access Token: GitHub Personal Access Token with appropriate repository permissions
Optional:
- GitHub Toolsets: Comma-separated list of enabled GitHub toolsets (e.g., repos,issues,pull_requests). Defaults to all
- Dynamic Toolsets: Set to 1 to enable dynamic tool discovery (beta feature)
- GitHub Enterprise Host: For GitHub Enterprise Server or Enterprise Cloud with data residency
Available Toolsets
The following toolsets are available (all enabled by default):
| Toolset | Description |
|---|---|
| context | Strongly recommended: Tools that provide context about the current user and GitHub context |
| actions | GitHub Actions workflows and CI/CD operations |
| code_security | Code security related tools, such as GitHub Code Scanning |
| dependabot | Dependabot tools |
| discussions | GitHub Discussions related tools |
| experiments | Experimental features that are not considered stable yet |
| issues | GitHub Issues related tools |
| notifications | GitHub Notifications related tools |
| orgs | GitHub Organization related tools |
| pull_requests | GitHub Pull Request related tools |
| repos | GitHub Repository related tools |
| secret_protection | Secret protection related tools, such as GitHub Secret Scanning |
| users | GitHub User related tools |
Configuration
Environment variables
| Variable | Description | Required |
|---|---|---|
GITHUB_PERSONAL_ACCESS_TOKEN | GitHub Personal Access Token used to authenticate with the GitHub API. Required for all GitHub operations. | Yes |
GITHUB_TOOLSETS | Comma-separated list of enabled GitHub toolsets (e.g. repos,issues,pull_requests,code_security,experiments,all). Optional, defaults to all. | No |
GITHUB_DYNAMIC_TOOLSETS | Set to 1 to enable dynamic tool discovery. Optional. | No |
GITHUB_HOST | GitHub Enterprise Server hostname (e.g. https://ghes.example.com). Optional, for GitHub Enterprise integration. | No |
Container runtime
- Image
ghcr.io/obot-platform/mcp-images/github:latest- Path
/- Port
8099