Hey, this is a known issue in versions 2.3.18+ and Early Access builds.
Key point: Browser automation in Cursor works through built-in tools and should NOT show up as a separate MCP server in Settings > MCP. When you see “No MCP resources available” after asking “@Browser is there browser tools?”, that’s expected because Browser isn’t MCP, it’s a built-in feature.
That said, in your version (2.4.0-pre.48 Early Access) there’s a regression and Browser automation may not work at all. The team is working on a fix, and the ticket is tracked here: Browser MCP Tools Not Available
Workaround: downgrade to 2.2.44, where Browser works reliably:
- Download here: Download · Cursor
Alternative: use the Playwright MCP for browser automation: GitHub - remorses/playwriter: MCP to control your Chrome window via extension. Runs Playwright code in a stateful sandbox.