Vibe MCP — Real Chrome, Remotely
MCP server · by VibeTechnologies
Drive your real, logged-in Chrome from any MCP client — even from a remote machine, no inbound port.
Install
Run one of the commands below, then add the client config underneath.
npx -y @vibebrowser/mcphttps://relay.api.vibebrowser.app/mcp/{session_id}Client configuration
Paste into Claude Desktop, Cursor (mcp.json), VS Code or any MCP client, then restart the client.
{
"mcpServers": {
"vibe-mcp-2": {
"command": "npx",
"args": [
"-y",
"@vibebrowser/mcp"
]
}
}
}About this server
Vibe MCP — Real Chrome, Remotely is listed in the Browser Automation category of the MCPNav directory. It is distributed as npm, Streamable HTTP and can be loaded by any client that speaks the Model Context Protocol.
Typical uses include giving your assistant scoped access to the corresponding service so it can answer questions and take actions with real data instead of guessing. Always review what a server can access before you enable it — see our MCP security guide.
Frequently asked questions
What is the Vibe MCP — Real Chrome, Remotely MCP server?＋
Vibe MCP — Real Chrome, Remotely is an MCP server by VibeTechnologies. Drive your real, logged-in Chrome from any MCP client — even from a remote machine, no inbound port.
How do I install Vibe MCP — Real Chrome, Remotely?＋
Install it with: npx -y @vibebrowser/mcp. Then add the JSON config to your client's MCP settings and restart the client.
Is Vibe MCP — Real Chrome, Remotely free to use?＋
The MCP server itself is free to install. The source is public on https://github.com/VibeTechnologies/vibe-mcp. Any third-party API it calls (such as a search or maps API) may require its own key and billing.
Which clients support Vibe MCP — Real Chrome, Remotely?＋
Any MCP-compatible client can use it, including Claude Desktop, Cursor, VS Code, Windsurf and custom agents.