-
Notifications
You must be signed in to change notification settings - Fork 210
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
Comments
I also have the same problem. |
2 similar comments
I also have the same problem. |
I also have the same problem. |
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. |
My node version is v20.17.0 and I also have the same problem. Yesterday, the MCP tool was working without any issues. |
@meisuTJU — I'm having exactly the same case. |
+1, I am experiencing this. |
npx @agentdeskai/browser-tools-server@1.2.0 |
@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. |
node -v ─╯ |
Did you run |
Hey, thanks for sharing! There are three components to run this MCP tool:
Do note the difference between:
After that, open up your chrome dev tools and then the BrowserToolsMCP panel. If you're still having issues try these steps:
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! |
The text was updated successfully, but these errors were encountered: