Skip to content

Clarification on running and testing BrowserTools MCP locally with server code using VSCode #124

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
benzntech opened this issue Mar 28, 2025 · 0 comments

Comments

@benzntech
Copy link

I’m trying to understand the correct setup to use this tool when working on a project in VSCode where the backend code runs locally (e.g., via localhost:3000). My objective is to monitor and analyze browser interactions or run audits using the MCP Chrome extension, but I’m not sure how to correctly connect the setup when running a local dev server.

Could you help clarify the following:
• What are the exact steps to follow if I’m using VSCode and testing my web app at http://localhost:3000?
• Should the browser extension automatically detect my localhost page, or are there manual steps to link it to the MCP and server tools?
• How can I verify that the extension and local server are correctly communicating with each other and with the MCP server?
• Are there any known limitations when running local server-based apps (e.g., with hot reload or frontend frameworks like Next.js)?

Thanks in advance for the guidance! 🙏
This will help streamline my testing workflow for local development.

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

1 participant