Skip to content

[ Bug ] chrome extension TypeError #113

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

Open
Juone2 opened this issue Mar 24, 2025 · 5 comments
Open

[ Bug ] chrome extension TypeError #113

Juone2 opened this issue Mar 24, 2025 · 5 comments

Comments

@Juone2
Copy link

Juone2 commented Mar 24, 2025

When will this chrome extension be fixed?
Image

@Juone2 Juone2 changed the title chrome extension type error chrome extension TypeError Mar 24, 2025
@Juone2 Juone2 changed the title chrome extension TypeError [ Bug ] chrome extension TypeError Mar 24, 2025
@vinitk-aveosoft
Copy link

I'm also getting the same issue

1 similar comment
@itzhangjia
Copy link

I'm also getting the same issue

@atsukifunaishi
Copy link

same

1 similar comment
@fangguen
Copy link

same

@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

6 participants