> ## Documentation Index
> Fetch the complete documentation index at: https://docs.augmentcode.com/llms.txt
> Use this file to discover all available pages before exploring further.
# GitHub Enterprise Server Setup
> Configure Augment GitHub App for GitHub Enterprise Server instances.
## GitHub Enterprise Server Support
Enterprise customers can connect Augment to self-hosted GitHub Enterprise Server instances. This enables organizations with on-premises GitHub deployments to benefit from Augment's capabilities while maintaining their existing infrastructure and security requirements.
GitHub Enterprise Server support requires the Enterprise plan. You must be an administrator of your GitHub Enterprise Server organization to complete the setup.
## Register and Install the GitHub Enterprise Server App
For GitHub Enterprise Server, you'll need to complete two steps: registration and installation.
### Step 1: Register the App
1. Visit one of the following configuration pages:
* [Code Review Configuration](https://app.augmentcode.com/settings/code-review) — for Code Review setup
* [MCP Configuration](https://app.augmentcode.com/mcp/configuration) — for Remote MCP Server setup
2. Click **Set up for GitHub Enterprise Server** button or the **GitHub Enterprise Server** option under **Add a Provider** dropdown.
3. Enter your **GitHub Enterprise Server URL** (e.g., `https://github.your-company.com`)
4. Enter your **Organization Name** on GitHub Enterprise Server
5. Click **Connect**
6. You'll be redirected to your GitHub Enterprise Server instance to complete the app registration
7. Review the app manifest and click **Create GitHub App** to register the app
### Step 2: Install the App
After registration is complete:
1. Return to the Augment configuration page
2. It should now show an **Install** button
3. Click **Install** to open your GitHub Enterprise Server page to continue the installation
4. Select the repositories you want to grant access to
5. Click **Install** to complete the installation
Once installed, you should see a green "Installed" badge in the GitHub Enterprise Server tab.
## Permissions Requested
The GitHub Enterprise Server app requests the same permissions as the Cloud app:
* **Contents, read-only**: Clone repositories
* **Pull Requests, read and write**: Read pull requests and post comments to pull requests
* **Issues, read-only**: Read top-level PRs / Issues
* **Organization Members, read-only**: Read members of an organization, to distinguish internal and external users and their access levels to Augment features
## Available Features
Once connected to GitHub Enterprise Server, you can use:
* **Augment Code Review** — automated PR reviews
* **Remote MCP Server** — cross-repo context for AI tools
* **Augment for Slack** — codebase-aware Slack bot
## Key Capabilities
* **Self-Hosted Integration**: Connect to your organization's GitHub Enterprise Server instance
* **Custom Registration**: Register a dedicated Augment GitHub App on your Enterprise Server
* **Same Features**: Access all Augment features available on GitHub Cloud
* **Unified Management**: Manage both Cloud and Enterprise Server installations from a single Augment tenant
## Network Requirements & Limitations
Augment's integration with GitHub Enterprise Server (GHES) requires bidirectional network connectivity. In certain enterprise network configurations that block inbound traffic to the GHES instance, Augment features that rely on the GitHub App will not function.
### Required Connectivity
For Augment's GitHub App integration to work, **both** of the following must be true:
| Direction | Purpose |
| ----------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| **GHES → Augment** (outbound from your network) | GHES must be able to send webhook events (e.g., `pull_request`, `push`) to Augment's public endpoint. |
| **Augment → GHES** (inbound to your network) | Augment must be able to call the GHES REST APIs to fetch pull request metadata, retrieve repository contents, and post review comments. |
If either direction is blocked by firewall or network policy, GitHub App–based functionality will not work.
### When GHES Integration Will Not Work
The GitHub App integration will not function if:
* GHES is accessible only inside a private VPN and does not allow inbound API access from Augment.
* Firewall rules block inbound HTTPS (port 443) traffic from Augment's IP ranges.
* GHES is deployed on private IP space (RFC 1918) with no public routing or private peering.
* Corporate policy prohibits external services from making API calls into GHES.
* TLS is configured using an internal/private Certificate Authority and custom CA trust is not provided.
In these configurations, Augment cannot fetch repository data or post results back to GHES directly.
**Installing the GitHub App does not bypass firewall restrictions.**
Even after a successful installation:
* **Webhooks** (GHES → Augment) may succeed if outbound traffic is allowed.
* **API calls** (Augment → GHES) required to read data and post comments will fail if inbound access is blocked.
## Next Steps
Now that you've set up GitHub Enterprise Server, you can configure additional features:
Set up automated code reviews for your repositories
Configure integrations for Augment Agent
Connect external context sources via Model Context Protocol
Set up Augment for Slack
## Need Help?
If you encounter any issues during setup, check out our [Troubleshooting](/codereview/troubleshooting) guide.