GitHub MCP Returns 403 'not authorized to use this Copilot feature' on Claude Code Web

What this error means

HTTP 403 "unauthorized: not authorized to use this Copilot feature" is a Claude Code failure pattern reported for developers trying to fix github mcp authentication failure on claude code web (remote/cloud sessions). Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Open issue on anthropics/claude-code#59953 (May 17, 2026, 2 days ago). Claude Code 2.1.143 on web session — GitHub MCP server HTTP endpoint returns 403 entitlement failure. OAuth fallback triggers misleading ‘Server Turned Down → Google Drive’ page ending in Authentication timeout. Reproducible 100% across multiple attempts. Accounts lack Copilot feature entitlement. No gh CLI available in web env. Critical for paid Claude Code users who depend on GitHub automation. Not in covered-errors (different from generic OAuth or remote MCP connect failures). Category: AI Coding Tools per mapping for Claude Code.

Common causes

• Open issue on anthropics/claude-code#59953 (May 17, 2026, 2 days ago). Claude Code 2.1.143 on web session — GitHub MCP server HTTP endpoint returns 403 entitlement failure. OAuth fallback triggers misleading ‘Server Turned Down → Google Drive’ page ending in Authentication timeout. Reproducible 100% across multiple attempts. Accounts lack Copilot feature entitlement. No gh CLI available in web env. Critical for paid Claude Code users who depend on GitHub automation. Not in covered-errors (different from generic OAuth or remote MCP connect failures). Category: AI Coding Tools per mapping for Claude Code.

Quick fixes

1. Confirm the exact error signature matches HTTP 403 "unauthorized: not authorized to use this Copilot feature".
2. Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
3. Verify the account session, API key, provider settings, and environment where the failing tool is running.

Platform/tool-specific checks

• Verify the command, editor, extension, or API client that produced the error.
• Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
• Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

1. Capture the exact error message and the command, editor action, or request that triggered it.
2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
3. Review the source evidence below and compare it with your environment.
4. Apply one change at a time and rerun the smallest failing action.
5. Keep the working fix documented for the team or deployment environment.

How to prevent it

• Keep provider/tool configuration documented.
• Record non-secret diagnostics such as tool version, provider name, model name, and command path.
• Add a lightweight check before CI or production workflows depend on the tool.

Sources checked

• https://github.com/anthropics/claude-code/issues/59953

Evidence note: Open issue on anthropics/claude-code#59953 (May 17, 2026, 2 days ago). Claude Code 2.1.143 on web session — GitHub MCP server HTTP endpoint returns 403 entitlement failure. OAuth fallback triggers misleading ‘Server Turned Down → Google Drive’ page ending in Authentication timeout. Reproducible 100% across multiple attempts. Accounts lack Copilot feature entitlement. No gh CLI available in web env. Critical for paid Claude Code users who depend on GitHub automation. Not in covered-errors (different from generic OAuth or remote MCP connect failures). Category: AI Coding Tools per mapping for Claude Code.

Related errors

• AI Coding Tools

FAQ

What should I check first?

Start with the exact HTTP 403 "unauthorized: not authorized to use this Copilot feature" text and the smallest action that reproduces it.

Can I ignore this error?

No. Treat it as a failed Claude Code workflow until the root cause is understood.

Is this guaranteed to have one fix?

No. The imported evidence supports the troubleshooting path above, but tool behavior can vary by account, plan, version, provider, and local configuration.

How do I know the fix worked?

Rerun the same command, editor action, or request. The fix is working when that action completes without HTTP 403 "unauthorized: not authorized to use this Copilot feature".