$ loading_
Control Windows Chrome from WSL for low-overhead web automation and debugging.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "chrome-local-mcp" yet — see the docs or source repo.
Use chrome-local-mcp to open the local dev site, go to the login page, enter a test account, click submit, capture console errors, failed network requests, and screenshots, then summarize the reproduction steps.
Browser action results, key error details, screenshot evidence, and a structured issue reproduction summary.
Using chrome-local-mcp, visit the staging site and run the signup, email verification, login, and logout flow in order; if any step fails, stop and report the page, button state, and error message.
A step-by-step validation report showing success status and detailed context for any failure.
Use chrome-local-mcp to open the target site and navigate to the payment page that needs human confirmation, pause before submitting, continue only after I confirm, and record the final page state.
A pausable workflow that waits for human confirmation, then continues and returns the final execution result and page record.
Control a real Chrome browser for browsing, interaction, and page reading.
Control Chrome and automate multi-session browsing through MCP clients.
Control Chrome DevTools with AI for debugging, screenshots, and script execution.
Control Chrome via MCP for browsing, form filling, screenshots, and logs.
Control and inspect live Chrome for automation, debugging, and performance analysis.
Control your signed-in Chrome browser for web automation and screenshots via MCP.