Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to discover browser connector server. Please ensure it's running. #95

Open
jianger666 opened this issue Mar 17, 2025 · 16 comments
Open

Comments

@jianger666
Copy link

Image

Image

@San-Shui
Copy link

I also have the same problem.

2 similar comments
@fatWill
Copy link

fatWill commented Mar 17, 2025

I also have the same problem.

@MuMuShy
Copy link

MuMuShy commented Mar 18, 2025

I also have the same problem.

@puchunjie
Copy link

I found the issue. The reason is that after starting browser-tools-mcp, it cannot detect the browser-tools-server. After checking the source code, I discovered that it uses fetch to check for availability. If your Node version is below 18, it doesn’t have built-in fetch. Upgrading your Node version to 18 or higher should resolve the problem.

@dariusz-wozniak
Copy link

My node version is v20.17.0 and I also have the same problem. Yesterday, the MCP tool was working without any issues.

@meisuTJU
Copy link

I also have the same problem.
Here in the Mcp configuration, a small green light has already appeared before. I have also started the local service locally through npx @agentdeskai/browser-tools-server@1.2.0. The plugin in the browser shows that it can already connect to the local server. However, it seems that the cursor cannot connect to the locally started server.
I don't why....

Image Image

@tedjames

@dariusz-wozniak
Copy link

@meisuTJU — I'm having exactly the same case.

@savabarbarov96
Copy link

+1, I am experiencing this.

@hjgeek
Copy link

hjgeek commented Mar 20, 2025

+1
my version is 1.2.0
Image

@dariusz-wozniak
Copy link

I solved the issue.

  1. Ensure you're running node v20.x.
  2. Run npx @agentdeskai/browser-tools-server@1.2.0.
  3. Verify connection in the Chrome extension:

Image

I also removed and re-added extension to the Chrome.

Works fine now:

Image

@ImBIOS
Copy link

ImBIOS commented Mar 21, 2025

npx @agentdeskai/browser-tools-server@1.2.0

https://browsertools.agentdesk.ai/installation

@meisuTJU
Copy link

@dariusz-wozniak So, is the key measure to solve the problem upgrading the version of node to v20.x?

@dariusz-wozniak
Copy link

@dariusz-wozniak So, is the key measure to solve the problem upgrading the version of node to v20.x?

Not sure to be honest, I've done all described steps at once and it helped.

@Wxw-Gu
Copy link

Wxw-Gu commented Mar 24, 2025

node -v ─╯
v20.18.1
is not working

@dariusz-wozniak
Copy link

dariusz-wozniak commented Mar 24, 2025

Did you run npx @agentdeskai/browser-tools-server@1.2.0 and verified connection in the Chrome extension?

@tedjames
Copy link
Contributor

Hey, thanks for sharing! There are three components to run this MCP tool:

  1. Install our chrome extension
  2. Install the MCP server from this command within your IDE (different IDE have different configs but this command is generally a good starting point; please reference your IDEs docs for the proper config setup): npx @agentdeskai/browser-tools-mcp@latest
  3. Open a new terminal and run this command: npx @agentdeskai/browser-tools-server@latest

Do note the difference between:

  • browser-tools-server (local nodejs server that's a middleware for gathering logs)
    and
  • browser-tools-mcp (MCP server that you install into your IDE that communicates w/ the extension + browser-tools-server)

After that, open up your chrome dev tools and then the BrowserToolsMCP panel.

If you're still having issues try these steps:

  • Quit / close down your browser. Not just the window but all of Chrome itself.
  • Restart the local node server (browser-tools-server)
  • Make sure you only have ONE instance of chrome dev tools panel open

After that, it should work but if it doesn't let me know and I can share some more steps to gather logs/info about the issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests