Vibe MCP — Real Chrome, Remotely

io.github.VibeTechnologies/vibe-mcpVersion 0.3.6

Drive your real, logged-in Chrome from any MCP client — even from a remote machine, no inbound port.

Status

Not checkedWe do not check this entry.

We could not refresh it, so this page shows the last copy.

Data from the official MCP Registry, checked by run.zero. How we check

Streamable HTTP

https://relay.api.vibebrowser.app/mcp/{session_id}Not checked

claude mcp add --transport http vibe-mcp 'https://relay.api.vibebrowser.app/mcp/<YOUR_SESSION_ID>'

Replace <YOUR_SESSION_ID> before running.

1
2
3

Settings > Connectors > Add custom connector
Name: vibe-mcp
Remote MCP server URL: https://relay.api.vibebrowser.app/mcp/<YOUR_SESSION_ID>

Replace <YOUR_SESSION_ID> before running.

{
  "mcpServers": {
    "vibe-mcp": {
      "url": "https://relay.api.vibebrowser.app/mcp/<YOUR_SESSION_ID>"
    }
  }
}

Replace <YOUR_SESSION_ID> before running.

code --add-mcp '{"name":"vibe-mcp","type":"http","url":"https://relay.api.vibebrowser.app/mcp/<YOUR_SESSION_ID>"}'

Replace <YOUR_SESSION_ID> before running.

Streamable HTTP

npm: @vibebrowser/mcp 0.3.6

Package only

claude mcp add vibe-mcp -- npx -y @vibebrowser/mcp@0.3.6

Built your own server? run.zero hosts MCP servers on European infrastructure.

No tool list available.

Registry status: Active
Published: Aug 21, 2026
Updated: Aug 21, 2026
Website: https://vibebrowser.app/⁠ (opens in a new tab)
Repository: https://github.com/VibeTechnologies/vibe-mcp⁠ (opens in a new tab)
Categories (suggested): Browser automationSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR: Not declared