QuotaGuard gives your GitHub MCP server two fixed egress IPs, so calls to the GitHub API clear an organization's IP allow list instead of failing with valid credentials attached.
A developer using GitHub's own remote MCP server hit this directly: correct authorization credentials, request denied anyway, because the organization's IP allow list didn't recognize the server's egress IP.
Register your two QuotaGuard IPs on the allow list once and every subsequent MCP call from that server passes.
This isn't a theoretical gap. It's a filed issue on GitHub's official remote MCP server, with the organization's own rejection message attached.
Issue #748 on github/github-mcp-server shows the exact response: "Although you appear to have the correct authorization credentials, the organization has an IP allow list enabled, and your IP address is not permitted to access this resource." The credentials were never the problem.
The developer's follow-up in that issue was direct: is there any way to whitelist the IP from this MCP server. A fixed egress IP is the direct answer, since the org's allow list needs a stable address to add.
GitHub Enterprise Cloud organizations can enable an IP allow list under organization security settings. Once enabled, it applies to personal access tokens, OAuth Apps, and GitHub App installation tokens alike, so no token type routes around it.
GitHub's allow list accepts CIDR ranges and multiple entries, which is flexible for static infrastructure and useless for infrastructure that doesn't have a fixed address to begin with.
Admins can add individual IPs or CIDR blocks, and multiple entries at once. That flexibility only helps if the MCP server's egress address is known and stable enough to write down.
Lambda, Cloud Run, Render, and most container platforms reassign the outbound IP on redeploys and scaling events. An allow list entry written for last week's IP fails the moment the platform rotates, with no warning until the next 403.
Organizations can allow GitHub Actions to bypass the IP allow list for workflow runs, but that exemption is specific to Actions runners. A self-hosted or third-party MCP server calling the GitHub API from outside Actions gets no such pass.
The fix matches what the GitHub issue thread was asking for: a fixed address to whitelist. QuotaGuard Static covers this for most MCP deployments; Shield is the call when the repository data itself is regulated.
Point your MCP server's outbound HTTP client at your QuotaGuard proxy URL. Both static IPs go live behind a load balancer immediately, and you add them to the organization's IP allow list once.
If your HTTP client supports per-host proxy configuration, send only calls to api.github.com through QuotaGuard. Everything else your MCP server does goes direct, which keeps unrelated traffic fast and easy to debug.
QuotaGuard Static and Shield both carry outbound HTTPS through a blind CONNECT tunnel and never decrypt the payload. Shield adds a TLS-encrypted customer-to-proxy hop, the right call if your MCP server's repository access touches PHI, payment data, or anything under a HIPAA, PCI-DSS, or SOC 2 requirement.
Common questions about GitHub Enterprise MCP static IPs and QuotaGuard. See the MCP server static IP overview for how this gate shows up across other enterprise systems.
Does my GitHub MCP server definitely need a static IP?
Only if the organization you're calling has an IP allow list enabled. GitHub's own remote MCP server repo has a filed issue showing exactly this failure with valid credentials, so it's a documented and real block, not a hypothetical.
Is there any way to whitelist my MCP server's IP with GitHub?
Yes, once it's fixed. GitHub's org-level IP allow list accepts individual IPs and CIDR ranges, added under organization security settings. The gap is that most cloud platforms don't give you a stable IP to add in the first place, which is what a proxy like QuotaGuard fixes.
How long does setup take?
About two minutes. Set your QuotaGuard proxy URL as the environment variable your MCP server's HTTP client reads, then add both static IPs to the organization's IP allow list. No code changes beyond the proxy configuration.
Does the allow list apply to personal access tokens and GitHub Apps the same way?
Yes. Once an organization enables the IP allow list, it applies to personal access tokens, OAuth Apps, and GitHub App installation tokens alike. No token type is exempt from the network-layer check.
Does GitHub Actions get an exemption I can use for my MCP server?
No. Organizations can exempt GitHub Actions runners from the IP allow list for workflow runs, but that exemption is specific to Actions. A self-hosted or third-party MCP server calling the API from outside Actions still needs its IP on the allow list.
Static or Shield for a GitHub MCP server?
Static is the right default for most repository access. Use Shield if your MCP server's repository data touches PHI, payment data, or anything under a HIPAA, PCI-DSS, or SOC 2 requirement, since Shield keeps the customer-to-proxy hop TLS-encrypted instead of plaintext.
Will my static IPs change if I redeploy or upgrade my plan?
No. Your two static IPs stay fixed through redeploys, scaling events, and plan upgrades or downgrades, so the allow list entry you set once keeps working without re-registration.
For over a decade, QuotaGuard has provided reliable, high-performance static IP and proxy solutions for cloud environments like Heroku, Kubernetes, and AWS.
Get the fixed identity and security your application needs today.