Free tools Windows power users keep installed
One-click scans. No signup required.
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
When Claude Code does not launch a browser for a remote MCP login, copy the authentication URL it displays and open that URL manually. Complete the provider’s sign-in and consent screens, then return to Claude Code and check the server in /mcp. This documented fallback applies to remote MCP servers using SSE or HTTP; it is separate from signing in to your Claude account.
What “the browser won’t open” means
Claude Code’s remote MCP authentication has several distinct stages. Claude Code must create an authorization URL, launch (or offer) that URL, receive the provider’s authorization result, and associate the result with the configured server. A failure at one stage does not prove that the next stage is broken.
![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)
- URL generation: Claude Code starts OAuth for the selected remote server.
- Browser launch: Claude Code attempts to open the URL in a browser.
- Provider login: You sign in and approve the requested access.
- Return to Claude Code: The server becomes authenticated and usable.
The symptom in this article is the second stage: no browser window appears. Anthropic’s documented remedy is not to reinstall Claude Code, clear browser data, or change your default browser. It is to copy the URL Claude Code provides and open it yourself.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Quick fix: copy the URL and open it manually
-
In Claude Code, enter
/mcpto open MCP management. -
Select the remote MCP server that needs authentication and start its authentication flow.
-
If no browser window appears, copy the complete authentication URL shown by Claude Code. Copy it exactly, including the query string.
-
Open a browser on the machine where you can complete the provider’s sign-in. Paste the URL into the address bar and navigate to it.
-
Sign in to the MCP provider, review the requested permissions, and approve the connection if you trust the server.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Return to Claude Code. Reopen
/mcpand verify that the server is authenticated, then try one of the server’s tools.
The manual step is a workaround for the launch action only. If the URL itself opens and the provider accepts the login, the browser-launch problem is resolved even though Claude Code did not create the window automatically.
If Claude Code does not show an authentication URL
A missing URL is different from a browser that fails to launch. First confirm that the server is configured and that you selected the intended remote entry in /mcp. The Claude Code CLI provides these inspection commands:
claude mcp listlists configured MCP servers.claude mcp get <name>displays the configuration for a named server.claude mcp remove <name>removes a server configuration when you need to add it again using the provider’s current instructions.
Replace <name> with the server name shown by claude mcp list. Check the server URL, transport, and any required headers or credentials against the provider’s instructions. Do not assume that a local configuration using standard input/output supports the same OAuth flow described for a remote server.
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 minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallRemote OAuth, SSE, HTTP, and local servers
The documented OAuth flow concerns remote MCP servers reached over SSE or HTTP. A local stdio server is started as a local process and may use an entirely different authentication method, such as an environment variable or a provider-specific setup command. Applying the remote-browser workaround to every MCP server can therefore send you looking in the wrong place.
Use the server’s configured transport as the diagnostic boundary. If claude mcp get <name> shows a remote HTTP or SSE endpoint, continue with the URL-and-browser procedure. If it shows a local command, consult that server’s authentication instructions instead of expecting Claude Code to open an OAuth page.
Diagnose the stage that fails
| Observed behavior | Likely stage | Next action |
|---|---|---|
| No window, but Claude Code prints a URL | Browser launch | Copy and open the URL manually. |
| No URL appears after starting authentication | Server configuration or OAuth initiation | Run claude mcp list and claude mcp get <name>; verify the remote endpoint and transport. |
| The URL opens but the provider rejects sign-in | Provider authorization | Follow the provider’s error message, required organization policy, scopes, or account requirements. |
| Login succeeds but Claude Code still shows unauthenticated | Return/callback or network path | Return to /mcp, inspect the server entry, and check proxy or certificate settings in managed environments. |
| The page cannot be reached | Network access | Check firewall, proxy, DNS, and certificate requirements for both Claude Code and the MCP provider. |
These observations are diagnostic branches, not proof of a particular cause. The browser symptom alone does not identify an operating-system setting, browser defect, or server bug.
Corporate proxies, certificates, and restricted networks
On a managed network, the browser and Claude Code can have different proxy settings. Anthropic documents the HTTP_PROXY and HTTPS_PROXY variables for proxy use. When a company proxy re-signs TLS traffic, the documented certificate variables are SSL_CERT_FILE and NODE_EXTRA_CA_CERTS. Configure these according to your organization’s approved certificate bundle; do not disable certificate verification.
Anthropic lists access to api.anthropic.com, statsig.anthropic.com, and sentry.io among Claude Code’s network requirements. That list is not a complete allowlist for the third-party MCP service you are authenticating. The remote server’s hostname and identity provider may require additional access.
Safe network checks
- Ask your network administrator whether outbound HTTPS to the MCP server and its identity provider is allowed.
- Confirm that the proxy variables are visible to the Claude Code process, not only to your graphical browser.
- Use the organization’s current CA bundle with the certificate variables when required.
- Record the exact hostname and error shown by the browser or Claude Code before requesting a firewall change.
A proxy is a reasonable check only when the environment is managed or the URL fails to load. The available documentation does not establish that a proxy causes every browser-launch failure.
When the URL opens but authentication still fails
Provider rejects the account
Some MCP providers restrict access by organization, role, domain, or approved OAuth scopes. Read the provider’s message and use the account authorized for that server. Claude Code’s generic browser fallback cannot override a provider policy.
Consent completes, but no return occurs
Keep the original Claude Code session open while completing authorization. If the provider offers a “return to application” link, use it. Then reopen /mcp and inspect the server. If the provider reports success but Claude Code does not, capture the callback error and check the network path, proxy, and certificate configuration.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Server appears authenticated but tool calls fail
Authentication proves that the OAuth exchange completed; it does not guarantee that every tool is enabled or that the remote service is healthy. Inspect the server configuration with claude mcp get <name>, verify required headers or scopes with the provider, and test a low-risk tool first.
Security checks before you paste an OAuth URL
- Make sure the hostname belongs to the MCP provider you intended to configure.
- Do not paste the URL into chat, issue trackers, or logs; authorization URLs can contain short-lived state or code parameters.
- Approve only scopes you understand and need.
- Use a private browser profile only if your organization permits it; do not bypass enterprise monitoring or certificate controls.
- Remove an obsolete configuration with
claude mcp remove <name>rather than leaving a stale remote entry active.
Or skip the browser setup
If your task is to capture a web page for documentation or an AI workflow rather than authenticate an MCP server, ScreenshotNeo provides a website screenshot API and MCP server. It accepts a URL and returns a PNG, JPEG, WebP, or PDF. Before capture it can accept cookie or consent banners and remove more than 60 known consent platforms, newsletter popups, and chat widgets; each cleanup step can be disabled. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies the page verdict and billing status in headers.
For a one-call capture, see the ScreenshotNeo API documentation:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython:
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js:
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);ScreenshotNeo also exposes MCP tools named take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients. Its plans include 1,000 screenshots per month free with no card; paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account to get started.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsFAQ
Is this the same as signing in to Claude Code?
No. The /mcp flow authenticates a remote MCP server. Claude Code account sign-in has separate account and enterprise authentication paths.
Can I use the workaround from another computer?
Only if the authorization flow and callback are supported by that setup. The safest path is to copy the URL from the active Claude Code session and complete it where the provider expects the callback, then return to that session.
Should I change my default browser?
Not as a first step. The documented fallback is to copy the supplied URL and open it manually; the available guidance does not require changing browser defaults.
What information should I provide when asking for support?
Report the server name, whether its transport is SSE or HTTP, the exact stage that fails, the browser error if any, and relevant proxy or certificate configuration. Never include access keys, authorization codes, cookies, or the full OAuth URL.
Frequently Asked Questions
Does manually opening the URL weaken OAuth security?
No. You are using the same authorization URL generated by Claude Code. Verify the provider hostname and requested scopes before approving access, and keep the URL private.
Why does authentication succeed in the browser but not in Claude Code?
The browser portion may have succeeded while the callback or Claude Code network path failed. Recheck the remote entry with claude mcp get <name> and investigate proxy, certificate, firewall, or provider callback requirements.
Does this procedure apply to every MCP transport?
No. The documented remote OAuth guidance applies to SSE and HTTP servers. Local stdio servers can use different authentication instructions.
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.
Recommended Free Tools
