Browser agent is not connecting

[emi-ran]

C:\Users\emiran>cmd /c npx -y @agentdeskai/browser-tools-mcp@1.2.0
Attempting initial server discovery on startup...
Starting server discovery process
Will try hosts: 127.0.0.1, 127.0.0.1, localhost
Will try ports: 3025, 3026, 3027, 3028, 3029, 3030, 3031, 3032, 3033, 3034, 3035
Checking 127.0.0.1:3025...
Error checking 127.0.0.1:3025: fetch failed
Checking 127.0.0.1:3026...
Error checking 127.0.0.1:3026: fetch failed
Checking 127.0.0.1:3027...
Error checking 127.0.0.1:3027: fetch failed
Checking 127.0.0.1:3028...
Error checking 127.0.0.1:3028: fetch failed
Checking 127.0.0.1:3029...
Error checking 127.0.0.1:3029: fetch failed
Checking 127.0.0.1:3030...
Error checking 127.0.0.1:3030: fetch failed
Checking 127.0.0.1:3031...
Error checking 127.0.0.1:3031: fetch failed
Checking 127.0.0.1:3032...
Error checking 127.0.0.1:3032: fetch failed
Checking 127.0.0.1:3033...
Error checking 127.0.0.1:3033: fetch failed
Checking 127.0.0.1:3034...
Error checking 127.0.0.1:3034: fetch failed
Checking 127.0.0.1:3035...
Error checking 127.0.0.1:3035: fetch failed
Checking 127.0.0.1:3025...
Error checking 127.0.0.1:3025: fetch failed
Checking 127.0.0.1:3026...
Error checking 127.0.0.1:3026: fetch failed
Checking 127.0.0.1:3027...
Error checking 127.0.0.1:3027: fetch failed
Checking 127.0.0.1:3028...
Error checking 127.0.0.1:3028: fetch failed
Checking 127.0.0.1:3029...
Error checking 127.0.0.1:3029: fetch failed
Checking 127.0.0.1:3030...
Error checking 127.0.0.1:3030: fetch failed
Checking 127.0.0.1:3031...
Error checking 127.0.0.1:3031: fetch failed
Checking 127.0.0.1:3032...
Error checking 127.0.0.1:3032: fetch failed
Checking 127.0.0.1:3033...
Error checking 127.0.0.1:3033: fetch failed
Checking 127.0.0.1:3034...
Error checking 127.0.0.1:3034: fetch failed
Checking 127.0.0.1:3035...
Error checking 127.0.0.1:3035: fetch failed
Checking localhost:3025...
Error checking localhost:3025: fetch failed
Checking localhost:3026...
Error checking localhost:3026: fetch failed
Checking localhost:3027...
Error checking localhost:3027: fetch failed
Checking localhost:3028...
Error checking localhost:3028: fetch failed
Checking localhost:3029...
Error checking localhost:3029: fetch failed
Checking localhost:3030...
Error checking localhost:3030: fetch failed
Checking localhost:3031...
Error checking localhost:3031: fetch failed
Checking localhost:3032...
Error checking localhost:3032: fetch failed
Checking localhost:3033...
Error checking localhost:3033: fetch failed
Checking localhost:3034...
Error checking localhost:3034: fetch failed
Checking localhost:3035...
Error checking localhost:3035: fetch failed
No server found during discovery
Initial server discovery failed. Will try again when tools are used.

I get this error when running the command:
cmd /c npx -y @agentdeskai/browser-tools-mcp@1.2.0

I have already added the browser extension, but here are the extension errors:

Error wiping logs: TypeError: Failed to fetch
Server identity validation failed: TypeError: Failed to fetch
Uncaught (in promise) Error: Extension context invalidated.
Error validating server identity: TypeError: Failed to fetch
Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
Error updating server with URL: Failed to fetch
Failed to update server with URL after 3 attempts

I can provide more details if someone can help.

[roune]

+1

[tedjames]

Are you running the browser-tools-server in a terminal as well?

[Messilimeng]

Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.

[chiuweilun1107]

+1

[Lichi002]

+1

[shaskola]

+1
I'm working on a hugo website

[ChaoTzuJung]

Base on the discussion
#86

I find it need to run npx @agentdeskai/browser-tools-server@1.2.0 first at Browser Tool MCP 1.2.0 version
And then it resolve the connecting error.

[sameronline]

Another method to run this on windows using docker with no deps but docker desktop itself/cli on other systems, probably going to work on any other system:

First run the server, in a separate command line:

docker run -it --rm -p 3025:3025 node:18-slim npx -y @agentdeskai/browser-tools-server@1.2.0

2nd in Cursor mcp.json use:

{
    "mcpServers": {
      "browser-tools": {
        "command": "docker",
        "args": [
          "run",
          "-i",
          "--init",
          "--network=host",
          "--rm",
          "node:18-slim",
          "npx",
          "--no-install-message",
          "--no-update-notifier",
          "--quiet",
          "@agentdeskai/browser-tools-mcp@1.2.0"
        ],
        "enabled": true
      }
    }
  }

that should be it!

[ai-rpcroke]

Yes same error. I tried all the variations of uninstalling, installing, clearing cache etc. and nothing works:

background.js:1 Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.

Any ideas? I am Chrome OS with all the latest versions of Cursor, Mac OS. The server works and Cursor is interfacing with it just fine. It is the browser.

[puchunjie]

Check the Node version, this requires 18+

[hy57in]

background.js:1 Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.

I have same error. I ran npx @agentdeskai/browser-tools-server@1.2.0 and npx @agentdeskai/browser-tools-mcp@1.2.0

[Namokar100]

after installing the browser-tools MCP, use this command in the new terminal in the project directory.
npx @agentdeskai/browser-tools-server@1.2.0.

Then check go to your browser --> Open developer options --> Then Navigate to BrowserTools MCP tab --> If you see Connected to browser-tools-server v1.2.0 at localhost:3025 then Then MCP is connected.

[matewz]

I got.
Just replacing:

"command": "wsl" to "command": "cmd",

Reference: https://www.youtube.com/watch?v=_19sK91rCSE&t=22s

{
  "mcpServers": {
    "browser-tools": {
      "command": "cmd",
      "args": [
        "bash",
        "-c",
        "cmd /c npx -y @agentdeskai/browser-tools-server@1.2.0"
      ],
      "enabled": true
    }
  }
}

[cwhsu1984]

It seems both browser-tools-server@1.2.0 and browser-tools-mcp@1.2.0 have issues right now.