Browser Tools fail to be called by Agent

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Browser tools not working, agent cannot connect to them - the dev tools show this error

ERR MCP tool execution error: Error: No server found with tool: browser_navigate: Error: MCP tool execution error: Error: No server found with tool: browser_navigate

Steps to Reproduce

Enter a prompt asking it to use the browser to navigate somewhere (select the built in browser as the target) - once acknowledged, it will ask to call the tool and then promptly fails.

Expected Behavior

It shouldn’t fail the call and should navigate to the requested address

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.43
VSCode Version: 1.99.3
Commit: 8e4da76ad196925accaa169efcae28c45454cce0
Date: 2025-10-30T18:49:27.589Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

1 Like
2

Yea, the internal browser has not been working very well at all. Even when it was able to browse, it said it cannot recognize Blazor elements on the page. The older version that was using normal browser was working super well.

3

Thanks for reporting this! This is a known issue with the new Browser Tab feature in Cursor 2.0 - the team is actively working on improvements and has shipped several fixes in recent updates.

Could you please share Request ID from the failed Agent interaction (context menu > Copy Request ID)

@Serp - Thanks for confirming the issue. Could you also share request ID if you’re seeing the same error?

1 Like
4

Today there is new kind problem. I did ask agent to see my page in location X.

  • With external browser it freezes to first “Planning next moves”.
  • With internal browser it first navigates to the page and then takes screenshot, and then freeze to the “Planning next moves”
5

Still getting lots of Failed to execute browser_navigate 8fceb0c5-6e60-462d-b310-3e955b7d7f12

6

cursor agent tab as well as cursor agent completely uanble to utilize the built in browser at all 6455308b-864c-4c32-a985-0d9ed11c3e66

7

Can confirm, this is happening for me across multiple models despite it being able to 1. See the tools, and 2. Browser Automation is green.

8

Request ID: 3334f2c4-d73d-4c05-88ea-4e616837a340

9

Any progress on this? I get “Process with MCP failed to execute tool browser_navigate” any time an agent tries to access a website. This seems like a pretty big bug to just leave open for weeks on end, no?

1 Like
10

image
image193Ă—126 2.88 KB

I updated to 2.1 in hopes that maybe now this feature has been fixed.
They broke it even more now….

The button Open Browser does nothing now..

EDIT: After going to settings and finding the browser settings.
I changed it from “Google Chrome” → Browser Tab

It is able to see and use the browser window in the IDE at-least.

1 Like
11

Having the same issue, the mcp server shows green and 26 tools enabled, but none of the agents are able to use any browser tool - show failed to execute tool browser_tabs
928060e3-d746-4a31-9275-64398b42c813

12

Broken for me as well, in the latest update.

Request id: e1c78d4f-53f4-46dd-a11f-adac0464557e

13

image
image1652Ă—862 161 KB

14

I found out that it starts working when I sign in with my private account.
And stops working again when I sign in with my company’s account. My company uses Enterprise plan so it seems that it’s disabled on our company side.
There is prob no proper error handling so it fails with these cryptic error messages.

1 Like
15

If you are on Enterprise plan, ask your admin to enable this

image
image1980Ă—502 40.2 KB

16

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.