Drive your real, logged-in Chrome from any MCP client — even from a remote machine, no inbound port.
Connect Remote server
claude mcp add --transport http vibe-mcp https://relay.api.vibebrowser.app/mcp/{session_id}
{
"mcpServers": {
"vibe-mcp": {
"url": "https://relay.api.vibebrowser.app/mcp/{session_id}"
}
}
}
{
"servers": {
"vibe-mcp": {
"type": "http",
"url": "https://relay.api.vibebrowser.app/mcp/{session_id}"
}
}
}
Settings > Connectors > Add custom connector
URL: https://relay.api.vibebrowser.app/mcp/{session_id}
Tools
The tool list was not available in our last check.
Details
| Endpoint | https://relay.api.vibebrowser.app/mcp/{session_id} (Streamable HTTP) |
| Package | @vibebrowser/[email protected] (NPM, stdio) |
| First published | 21 Aug 2026 |
| Last updated | 21 Aug 2026 |
| Registry name | io.github.VibeTechnologies/vibe-mcp |
More browser automation servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
