Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →If Claude Code does not launch a browser while authenticating a remote MCP server, copy the authentication URL shown by Claude Code and open it yourself. Complete the provider’s sign-in and consent page, then return to Claude Code and check the server in /mcp. This is the documented fallback for the automatic-launch symptom; it does not require changing your default browser, clearing browser data, or reinstalling Claude Code.
What this error actually means
The browser step belongs to OAuth authentication for a remote MCP server. It is separate from signing in to your Claude account. Claude Code account authentication has its own account and enterprise sign-in paths; a successful Claude login does not automatically authorize every remote MCP server.
![Claude AI for Beginners Bible: [5 in 1] The Ultimate Guide to Automate Your Work, Save Hours Every Week, and Use AI for Real-World Results](https://m.media-amazon.com/images/I/415+fSJacsL._SL160_.jpg)
Anthropic documents this OAuth flow for remote MCP servers using the SSE or HTTP transport. Do not assume that the same browser workflow applies to every local MCP server that uses stdio. A local server may have entirely different credentials or configuration.
Fastest fix: copy the URL and open it manually
- In Claude Code, enter
/mcpto open MCP management. - Select the remote server that requires authentication and start its authentication flow.
- Wait for Claude Code to display an authentication URL. If no browser window appears, select and copy that URL.
- Paste the URL into a browser yourself. Use a browser that can reach the MCP provider and any identity provider it redirects to.
- Sign in, review the requested permissions, and approve the authorization on the provider’s page.
- Return to Claude Code. Use
/mcpagain to confirm that the server now reports an authenticated state, then try an operation that uses the server.
The manual-open step is the direct remedy for a failed automatic browser launch. The documentation does not identify one universal cause for the launch failure, so avoid treating a particular operating-system setting, default-browser preference, or security product as the cause without evidence from your machine.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Check the server entry from the command line
If the URL opens but Claude Code still cannot use the server, inspect the MCP configuration. These commands show what Claude Code believes is configured; they do not replace the provider’s own authorization requirements.
claude mcp list
claude mcp get <name>Replace <name> with the server name exactly as it appears in the list. Check the endpoint, transport, and any options that identify the remote service. If the entry is obsolete or points to the wrong server, remove that configuration and add the correct one using the setup instructions supplied by that MCP provider.
claude mcp remove <name>Removing a configuration does not prove that authentication was the problem; it simply gives you a clean way to correct an entry you have verified is wrong. Record the endpoint and required settings before removing anything so you can recreate it accurately.
Find the stage that is failing
| Stage | What you see | What to do |
|---|---|---|
| URL generation | No URL appears after you start authentication. | Reopen /mcp, select the intended remote server, and start authentication again. If the server never produces a URL, inspect its entry with claude mcp get <name> and consult that provider’s authorization requirements. |
| Automatic launch | A URL is displayed, but no browser window opens. | Copy the displayed URL and open it manually. This is the documented fallback. |
| Provider sign-in | The URL opens, but the identity provider rejects the login or consent. | Follow the provider’s sign-in requirements. The behavior of every third-party MCP provider is not defined by Claude Code’s general documentation. |
| Return to Claude Code | Browser approval succeeds, but the server remains unauthenticated. | Return to /mcp, verify the same server name and endpoint, and inspect the entry with claude mcp get <name>. A mismatch between the authorized endpoint and the configured endpoint is a reasonable configuration check. |
| Tool request | The server appears authenticated, but a tool call fails. | Separate authentication from authorization and server availability. Confirm that the account has permission for the requested operation and that the remote service is reachable from your network. |
When a managed network is involved
If manually opening the URL also fails, investigate the network only after confirming that the URL itself is correct. Corporate proxies, TLS inspection, firewalls, and custom certificate authorities can affect Claude Code or the identity provider. Anthropic documents these environment variables for Claude Code:
Recommended Free Tools
HTTP_PROXYandHTTPS_PROXYfor proxy routing.SSL_CERT_FILEandNODE_EXTRA_CA_CERTSwhen your organization requires a custom certificate bundle.
Configure them according to your organization’s proxy and certificate instructions, then restart Claude Code and retry the /mcp flow. Do not copy a certificate path from another machine: the file must exist locally and contain the certificate authority your network requires.
Anthropic lists api.anthropic.com, statsig.anthropic.com, and sentry.io among Claude Code’s network requirements. That list describes Claude Code’s stated services, not a complete allowlist for the third-party MCP server you are authorizing. The remote provider and its identity service may require additional hostnames. Ask your network administrator for the provider-specific allowlist rather than broadly disabling TLS inspection or firewall controls.
Common symptoms and targeted fixes
A browser never opens, but Claude Code prints a URL
Use the URL as printed. Copy it without adding spaces or line breaks, paste it into a browser, and complete the flow there. The symptom alone does not establish whether the cause is a desktop integration, a headless session, a remote terminal, or a managed policy.
The copied URL shows an error immediately
Start a fresh authentication attempt from /mcp and copy the newly displayed URL. If the new URL fails in the same way, capture the exact error text and check the remote server’s documented OAuth requirements. Do not infer that clearing browser cookies or changing the default browser will fix a provider-side authorization error.
Sign-in succeeds, but Claude Code reports no authentication
Confirm that you authorized the same remote server represented by the configured endpoint. Then run claude mcp get <name> and compare the endpoint and transport with the provider’s setup instructions. If your organization uses separate accounts or tenants, make sure the browser session is signed in to the account that has access to that server.
The flow works on one network but not another
That pattern makes a proxy, firewall, DNS policy, or custom certificate a reasonable investigation target, but it is not proof of a particular cause. Compare whether the browser can reach the provider and identity service on the failing network, then apply the documented proxy or certificate settings for Claude Code.
The server is local rather than remote
Confirm the transport before applying this guide. The documented browser OAuth instructions concern remote SSE and HTTP servers. A local stdio server may require an API key, environment variable, or configuration file instead; use that server’s setup instructions and inspect its Claude Code entry with claude mcp get <name>.
Security checks before you authorize
- Verify that the URL’s domain is the MCP provider or its declared identity provider before entering credentials.
- Review the permission screen and grant only the scopes your work requires.
- Do not paste an OAuth URL, access token, or authorization code into an issue tracker or chat room.
- On a shared machine, sign out of the wrong browser account before approving access for a different organization or tenant.
- Do not disable certificate validation, endpoint security, or corporate controls merely because automatic browser launching failed.
Reliability and recovery checklist
- Confirm that the server is remote and uses SSE or HTTP for the documented OAuth flow.
- Open
/mcpand begin authentication for the correct server. - Copy and manually open the displayed URL when no browser window launches.
- Finish sign-in and consent in the browser, then return to Claude Code.
- Use
claude mcp listandclaude mcp get <name>to verify the configured server. - If the manual URL also fails, record the exact browser and Claude Code messages, then investigate provider authorization and managed-network access.
- Remove and recreate the entry only when you have confirmed that its endpoint or settings are incorrect.
This sequence keeps the diagnosis tied to the stage that failed. It also avoids destructive changes until you know that the configuration, rather than the browser launch integration or network, is at fault.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsOr skip the browser setup
If what you need is a clean image or PDF of an MCP provider’s documentation, consent page, or troubleshooting screen—not OAuth authorization itself—ScreenshotNeo can capture a URL with one request. It accepts consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each cleanup step can be disabled. Only clean shots are billed: bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are free, and the response identifies the result with X-Page-Verdict and X-Billed headers. ScreenshotNeo also has an MCP server with take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients.
See the ScreenshotNeo documentation for all options. A minimal request is:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://claude.ai -o shot.webpPython:
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://claude.ai"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js:
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://claude.ai' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);The Free plan includes 1,000 shots per month with no card. Paid plans start at $5 for 3,000 shots; every feature is included on every plan, and yearly billing provides two months free. These captures do not replace the manual OAuth approval described above; they simply remove browser setup when you need a page image or PDF. Create a free ScreenshotNeo account to start without a card.
FAQ
Is this the same as being unable to sign in to Claude Code?
No. The documented /mcp flow authorizes a remote MCP server. Claude Code account sign-in is a separate authentication process.
Does manual URL opening work for every MCP transport?
The cited OAuth guidance covers remote SSE and HTTP servers. It should not be generalized to local stdio servers without checking that server’s instructions.
Should I change my default browser first?
No. The documented workaround is to copy the URL Claude Code provides and open it manually. Change browser settings only if your own environment identifies a separate policy or integration problem.
Who can explain an authorization error after the page opens?
The remote MCP provider or identity provider controls its sign-in, account, and permission rules. Claude Code’s general MCP instructions cannot establish the behavior of every third-party service.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
