GitHub Enterprise MCP

GitHub's own remote MCP server repository has a filed issue showing this exact failure: valid authorization credentials, request denied, because the organization's IP allow list didn't recognize the caller's IP. QuotaGuard has provided static IPs for cloud infrastructure since 2013.

GitHub Enterprise Cloud organizations that enable an IP allow list apply it to personal access tokens, OAuth Apps, and GitHub App installation tokens alike. An MCP server running on Lambda, Cloud Run, Render, or any container platform gets a rotating egress IP that fails this check regardless of token type or credential validity.

• Two-Minute Setup: Set your QuotaGuard proxy URL as the environment variable your MCP server's HTTP client reads for outbound calls, then add both static IPs to the organization's IP allow list under security settings.
• GitHub's Own MCP Server Repo Documents the Failure: Issue #748 on github/github-mcp-server shows a developer hitting this exact block with valid credentials, and asking directly whether the MCP server's IP can be whitelisted.
• CIDR Ranges and Multiple Entries Supported: GitHub's allow list accepts individual IPs or CIDR blocks. QuotaGuard's two static IPs are stable addresses that fit directly into that allow list.
• Production-Grade Reliability: A load-balanced pair of static IPs with automated failover. Both IPs go on the GitHub allow list, and traffic routes through whichever responds first.
• Shield for Regulated Repository Data: For PHI, payment data, or HIPAA/PCI/SOC 2-bound workloads, QuotaGuard Shield uses SSL passthrough so QuotaGuard never decrypts the data flowing between your MCP server and GitHub.

Actions exemption nuance: Organizations can exempt GitHub Actions runners from the IP allow list for workflow runs, but that exemption doesn't extend to self-hosted or third-party MCP servers calling the API from outside Actions. Those still need their IP on the allow list.