Bug report with browser extension

[Bilel_Rais]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Browser automation tools aren’t accessible, even though the Tools panel shows “Browser Automation: Ready (Chrome detected)”.
Environment:
Operating System: Windows (after restart)
Using Agent mode in the standard Cursor editor window
Browser Automation status: “Ready (Chrome detected)”
Chrome is installed and running
Server running locally on port 8889
Problem:
When attempting to use browser automation tools, they are not found. For example:
mcp_cursor-browser-extension_browser_navigate → Tool not found
mcp_cursor-browser-extension_browser_snapshot → Tool not found
All other browser tools → Not found

Error message:
Error calling tool: Tool mcp_cursor-browser-extension_browser_navigate not found.
Available tools: [“codebase_search”,“run_terminal_cmd”,“grep”,“delete_file”,…]

What I’ve tried:
Restarting Cursor
Restarting Windows
Verifying Chrome is running
Using call_mcp_tool with different server identifiers (cursor-browser-extension, browser-automation, browser, etc.)
Checking settings — Browser Automation shows “Ready”
Using Agent mode in the standard editor (not a separate Agent Window)
Expected behavior:
Browser automation tools should be available when the status shows “Ready (Chrome detected)”, allowing me to:
Navigate to URLs
Take page snapshots
Click elements
Type in inputs
Run JavaScript
Check console messages
View network requests
Impact:
Cannot perform automated browser testing. I need to verify UI functionality and performance improvements, but cannot interact with the browser programmatically.

is there any workaround?

Steps to Reproduce

Open Cursor IDE
Ensure Chrome is installed and running
Open Settings → Tools & MCP
Verify Browser Automation shows “Ready (Chrome detected)”
Switch to Agent mode (not a separate Agent Window, but Agent mode in the main editor)
Attempt to use browser automation tools by calling:
mcp_cursor-browser-extension_browser_navigate({url: “http://localhost:8889”})
Or any other browser tool like browser_snapshot, browser_click, etc.

Observe the error: “Tool mcp_cursor-browser-extension_browser_navigate not found”

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.21 (system setup)
VSCode Version: 1.105.1
Commit: 68e0a0385b87408d050869ea543e3778ad53f780
Date: 2026-01-02T23:46:13.381Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Model name: Opus 4.5

Additional Information

This issue started since the 2.3.18 update. When I install 2.3.15 the issue solves.

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

Hey, thanks for the report.

This is a known issue, and the team is working on a fix. We’ve gotten similar reports from other users with the same symptom.

While we work on the fix, can you confirm a couple things:

• In Settings > MCP, do you see any browser-related servers? What status do they show?

You mentioned it works on 2.3.15, which is really helpful for debugging the regression.

[Bilel_Rais]

Hey Dean,

Apologies for the wrong information. The latest release without this issue turned out to be Version: 2.2.44.

This is what my MCP settings show:

Best,
Bilel

[deanrie]

Thanks for the screenshot.

I can see only context7 and firecrawl-mcp in the list, and both are disabled. That’s normal. Browser automation shouldn’t show up there as a separate MCP server. It works through built-in tools.

For debugging, you can try:

• Open Help > Toggle Developer Tools > Console
• Try calling the browser tool in the Agent
• Copy any errors from the console

I’ll pass this to the team as a regression. 2.2.44 works, but 2.3.18+ is broken. If you can grab logs, it’ll speed up the fix.

[Bilel_Rais]

Hopefully this helps!

[deanrie]

Thanks for the console logs. I can see a screenshot showing OTLPExporterError messages. These errors are related to Cursor telemetry and shouldn’t affect the main functionality.

The main issue with the browser automation tools has already been reported to the dev team as a regression after version 2.2.44. These telemetry errors might be related to the same issue.

While the team is working on a fix, you can keep using version 2.2.44, where everything works correctly.

[Nikhil_Cheerla]

Any update on this bug?