Unable to use Browser Automation features

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

My agent is able to list and call the browser automation tools, but all of those tool calls fail with an errors such as: Process with MCP failed to execute tool browser_snapshot.

Both “MCP: cursor-browser-extension” and “MCP: cursor-ide-browser” output panels display the following logs:

2025-12-16 22:17:02.654 [info] Handling GetInstructions action
2025-12-16 22:17:02.654 [error] No server info found

I have tried both “Browser Tab” and “Google Chrome” mode settings. Both give the same errors.

Steps to Reproduce

  1. Configure Browser Automation setting to “Browser Tab”
  2. Ask the agent: @browser What do you see on the screen?
  3. Observe Process with MCP failed to execute tool browser_snapshot error in thinking block

Expected Behavior

Browser features should work as described.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.20
VSCode Version: 1.105.1
Commit: b3573281c4775bfc6bba466bf6563d3d498d1070
Date: 2025-12-12T06:29:26.017Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

Additional Information

I am an enterprise user.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

2

Hey, thanks for the report. The “No server info found” error means the MCP browser-automation server failed to initialize properly. This is a known issue in 2.2.20 with Browser Tab mode.

Similar reports here: Cursor 2.1 Agent can't access in-IDE browser

Try these for now:

  • Fully restart Cursor (completely end the process, not just close windows) - this often fixes MCP initialization
  • Clear npx cache: open terminal and run rm -rf ~/.npm/_npx, then restart Cursor
  • Switch to Google Chrome mode instead of Browser Tab in Settings > Agent > Browser mode - this can help until Tab mode is fixed
  • Check Settings > Tools & MCP - disable Browser Automation, then enable it again
  • If using VPN/proxy - disable it and try again

If the error persists, attach the Request ID from the browser-automation attempt. This will help engineers track the issue.

Browser not working
3

  • Fully restart Cursor (completely end the process, not just close windows) - this often fixes MCP initialization

  • Clear npx cache: open terminal and run rm -rf ~/.npm/_npx, then restart Cursor

After I followed these two steps I see a new message that I didn’t have before:

Screenshot 2025-12-17 at 5.25.33 PM

So that could explain why it didn’t work.

This seems like a visual bug for Cursor: the backend was disabled by the enterprise, but the UI state didn’t reflect this until I restarted Cursor after I turned the feature “Off” first.

I will follow up with my IT team on getting the feature enabled.

Thanks!