Browser MCP not working: Browser icon missing and Agent cannot control the browser

Description:

Issue: The Browser MCP seems to be broken. The browser icon is missing from the bottom right of the Agent/Chat interface (I recall seeing it before, but never used it). Despite multiple attempts, I cannot get the Agent to control the browser.

Steps I’ve taken:

  1. Reinstalled Cursor.

  2. Restarted the system.

  3. Tried toggling MCP settings.

Technical Observations:

  • The “Cursor IDE Browser Automation” only stops showing errors if I manually open a Browser Tab before executing “Reload Window”. However, even when the error disappears, the Agent still cannot interact with or “see” the browser.

  • I have spent over 2 hours troubleshooting this with no success.

Questions: How can I properly enable the Browser MCP so it’s accessible and controllable by the Agent? Are there specific logs I should check to see why the icon is missing?

System Info:

  • Cursor Version: 2.6.21

  • OS: Windows 11

  • Terminal: CMD

Hi Archie. Have you tried the solution outlined in this post Agent can't use Browser MCP - #3 by deanrie ?

Already tried, and even rebooted the Windows.

Today I tried on Ubuntu, also no luck.

The Browser MCP is not working on Mac Book Pro as well. V2.6.19.

Hey, thanks for the report and the detailed screenshots. I can see the browser-use sub-agent says tools are unavailable, even though the extension logs show a successful connection.

This is a recurring issue we’ve fixed a few times, but since you’re seeing it on 2.6.21 across three different OSes (Windows, Ubuntu, Mac), it might be a new regression.

Do you have any third-party browser or MCP extensions installed? Please try disabling them to rule out conflicts.

I also need:

  • The Request ID from a failed chat: top right three-dot menu > Copy Request ID
  • Any errors from the Console: Help > Toggle Developer Tools > Console tab, then try using the browser tool and see if any red errors show up

Your report across 3 OSes is really helpful context. Let me know what you find in the console.

Since 3 OSes all have the issue. I think you should be able to let Agents to reproduce the issue and fix it.

2.6.22 still has the issue.