$ loading_
Remotely control your real logged-in Chrome from any MCP client.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "Vibe MCP — Real Chrome, Remotely" MCP server from askskill: Run: claude mcp add 'io-github-vibetechnologies-vibe-mcp' -- npx -y @vibebrowser/mcp
Developers or researchers can control their real logged-in Chrome from an MCP client running on a remote machine. This avoids re-authentication and enables web actions within an existing browser session.
This tool enables remote browser control even when opening inbound ports is not practical. It fits scenarios where a local Chrome session must be accessed across machines.
When page inspection or clicking must happen in a real browser rather than a simulated environment, this tool can help. It is especially useful for web tasks that depend on the current browser login state.
It lets you remotely control a real Chrome browser from any MCP client while using the existing logged-in session. The description also states that it works even from a remote machine without requiring an inbound port.
Based on the provided description, no inbound port is required. That is a key difference from some traditional remote connection approaches.
Yes. The description explicitly says it drives your real, logged-in Chrome. For exact installation and connection steps, see the source repository.
Control a real Chrome browser for browsing, interaction, and page reading.
Control and inspect a live Chrome browser for automation, debugging, and performance analysis.
Control Chrome locally or remotely to automate browsing, forms, screenshots, and scripts.
Control a local Chrome browser for web automation, testing, and data capture.
Control Chrome locally for navigation, page reading, and browser interaction automation.
Control Chrome via MCP for browsing, form filling, screenshots, and logs.