Vibe MCP — Real Chrome, Remotely

io.github.VibeTechnologies/vibe-mcp

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

Connect this server

Add this to your MCP client config — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor).Suits: Claude Desktop · Cursor.

{
  "mcpServers": {
    "vibe-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@vibebrowser/mcp@0.3.6"
      ]
    }
  }
}

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Developer Tools
Version
0.3.6
Registry
active
Published
8/21/2026

Remotes

  • streamable-httphttps://relay.api.vibebrowser.app/mcp/{session_id}
Browse all Developer Tools →

Add the badge to your site

Show visitors that Vibe MCP — Real Chrome, Remotely is listed here — it’s also the link we check for a free listing.

Vibe MCP — Real Chrome, Remotely — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-vibetechnologies-vibe-mcp?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Vibe MCP — Real Chrome, Remotely — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![Vibe MCP — Real Chrome, Remotely — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-vibetechnologies-vibe-mcp?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.