Claude Code / AI Coding Tools

GitHub MCP OAuth Flow Fails on claude.ai/code — Private Repo Access Broken

Developer using Claude Code web (claude.ai/code) wants GitHub MCP tools to access private repositories but OAuth login flow silently breaks or returns inconsistent results Includes evidence for Claude Code troubleshooting demand.

Source-backed Last updated May 19, 2026 3 sources Needs local verification

Category: AI Coding Tools
Error signature: [BUG] GitHub MCP OAuth flow fails on claude.ai/code web client — inconsistently provides GitHub MCP tools for private repos
Quick fix: Verify the account session, API key, provider settings, and environment where the failing tool is running.
Updated: May 19, 2026
Verification status: Source-backed
Evidence: 3 public source URLs

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for Claude Code, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

[BUG] GitHub MCP OAuth flow fails on claude.ai/code web client — inconsistently provides GitHub MCP tools for private repos is a Claude Code failure pattern reported for developers trying to developer using claude code web (claude.ai/code) wants github mcp tools to access private repositories but oauth login flow silently breaks or returns inconsistent results. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Found on GitHub: anthropics/claude-code#45100 (Apr 2026). Very recent issue about Claude Code web inconsistently providing GitHub MCP tools. Related issues include #3433 (cannot connect to GitHub remote MCP server using OAuth) and #26917 (HTTP MCP servers requiring OAuth silently fail). Same error pattern across multiple dates shows persistent problem.

Common causes

Found on GitHub: anthropics/claude-code#45100 (Apr 2026). Very recent issue about Claude Code web inconsistently providing GitHub MCP tools. Related issues include #3433 (cannot connect to GitHub remote MCP server using OAuth) and #26917 (HTTP MCP servers requiring OAuth silently fail). Same error pattern across multiple dates shows persistent problem.

Quick fixes

Confirm the exact error signature matches [BUG] GitHub MCP OAuth flow fails on claude.ai/code web client — inconsistently provides GitHub MCP tools for private repos.
Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
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

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
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.

Diagnostic flow for this page

Match [BUG] GitHub MCP OAuth flow fails on claude.ai/code web client — inconsistently provides GitHub MCP tools for private repos exactly before applying the quick fix.
Compare the failing environment with Claude Code versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does [BUG] GitHub MCP OAuth flow fails on claude.ai/code web client — inconsistently provides GitHub MCP tools for private repos mean in Claude Code?

[BUG] GitHub MCP OAuth flow fails on claude.ai/code web client — inconsistently provides GitHub MCP tools for private repos indicates the workflow described by "GitHub MCP OAuth Flow Fails on claude.ai/code — Private Repo Access Broken" failed in a AI Coding Tools context. Start by confirming the exact signature and the component that emitted it.

What should I check first for [BUG] GitHub MCP OAuth flow fails on claude.ai/code web client — inconsistently provides GitHub MCP tools for private repos?

Check whether this cause matches your environment: Found on GitHub: anthropics/claude-code#45100 (Apr 2026). Very recent issue about Claude Code web inconsistently providing GitHub MCP tools. Related issues include #3433 (cannot connect to GitHub remote MCP server using OAuth) and #26917 (HTTP MCP servers requiring OAuth silently fail). Same error pattern across multiple dates shows persistent problem.

Is the [BUG] GitHub MCP OAuth flow fails on claude.ai/code web client — inconsistently provides GitHub MCP tools for private repos guidance source-backed?

The "GitHub MCP OAuth Flow Fails on claude.ai/code — Private Repo Access Broken" page is labeled source-backed. It has 3 public source URLs from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for [BUG] GitHub MCP OAuth flow fails on claude.ai/code web client — inconsistently provides GitHub MCP tools for private repos?

For "GitHub MCP OAuth Flow Fails on claude.ai/code — Private Repo Access Broken", avoid applying "Verify the account session, API key, provider settings, and environment where the failing tool is running." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging [BUG] GitHub MCP OAuth flow fails on claude.ai/code web client — inconsistently provides GitHub MCP tools for private repos?

For "GitHub MCP OAuth Flow Fails on claude.ai/code — Private Repo Access Broken", collect the failing Claude Code command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.