Claude Code / AI Coding Tools

Claude Code MCP auth fails to launch browser automatically on Windows

Fix Claude Code MCP OAuth flow on Windows where the first MCP auth may work but subsequent ones silently fail due to browser not auto-launching; regression identified Includes evidence for Claude Code troubleshooting demand.

Source-backed Last updated May 19, 2026 1 source Needs local verification

Category: AI Coding Tools
Error signature: [BUG] mcp auth not automatically launching browser on Windows — subsequent MCP integrations (Atlassian, DataDog, Slack) fail because browser auth dialog never opens
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: 1 public source URL

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] mcp auth not automatically launching browser on Windows — subsequent MCP integrations (Atlassian, DataDog, Slack) fail because browser auth dialog never opens is a Claude Code failure pattern reported for developers trying to fix claude code mcp oauth flow on windows where the first mcp auth may work but subsequent ones silently fail due to browser not auto-launching; regression identified. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub Issue #59194 in anthropics/claude-code (opened May 15 2026, defconmike). Regression bug affecting Windows users. First MCP auth launches browser fine, subsequent ones (DataDog, Atlassian, Slack) fail without browser dialog. Tagged as regression + has repro. Directly impacts developers using Claude Code with MCP ecosystem integrations. Category mapping: AI Coding Tools (Claude Code MCP auth integration failure).

Common causes

GitHub Issue #59194 in anthropics/claude-code (opened May 15 2026, defconmike). Regression bug affecting Windows users. First MCP auth launches browser fine, subsequent ones (DataDog, Atlassian, Slack) fail without browser dialog. Tagged as regression + has repro. Directly impacts developers using Claude Code with MCP ecosystem integrations. Category mapping: AI Coding Tools (Claude Code MCP auth integration failure).

Quick fixes

Confirm the exact error signature matches [BUG] mcp auth not automatically launching browser on Windows — subsequent MCP integrations (Atlassian, DataDog, Slack) fail because browser auth dialog never opens.
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] mcp auth not automatically launching browser on Windows — subsequent MCP integrations (Atlassian, DataDog, Slack) fail because browser auth dialog never opens 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] mcp auth not automatically launching browser on Windows — subsequent MCP integrations (Atlassian, DataDog, Slack) fail because browser auth dialog never opens mean in Claude Code?

[BUG] mcp auth not automatically launching browser on Windows — subsequent MCP integrations (Atlassian, DataDog, Slack) fail because browser auth dialog never opens indicates the workflow described by "Claude Code MCP auth fails to launch browser automatically on Windows" 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] mcp auth not automatically launching browser on Windows — subsequent MCP integrations (Atlassian, DataDog, Slack) fail because browser auth dialog never opens?

Check whether this cause matches your environment: GitHub Issue #59194 in anthropics/claude-code (opened May 15 2026, defconmike). Regression bug affecting Windows users. First MCP auth launches browser fine, subsequent ones (DataDog, Atlassian, Slack) fail without browser dialog. Tagged as regression + has repro. Directly impacts developers using Claude Code with MCP ecosystem integrations. Category mapping: AI Coding Tools (Claude Code MCP auth integration failure).

Is the [BUG] mcp auth not automatically launching browser on Windows — subsequent MCP integrations (Atlassian, DataDog, Slack) fail because browser auth dialog never opens guidance source-backed?

The "Claude Code MCP auth fails to launch browser automatically on Windows" page is labeled source-backed. It has 1 public source URL 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] mcp auth not automatically launching browser on Windows — subsequent MCP integrations (Atlassian, DataDog, Slack) fail because browser auth dialog never opens?

For "Claude Code MCP auth fails to launch browser automatically on Windows", 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] mcp auth not automatically launching browser on Windows — subsequent MCP integrations (Atlassian, DataDog, Slack) fail because browser auth dialog never opens?

For "Claude Code MCP auth fails to launch browser automatically on Windows", 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.