Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Vibe MCP — Real Chrome, Remotely

by VibeTechnologiesversion 0.3.6i★ 3iComputer or cloudOfficial site ↗
Registry nameio.github.VibeTechnologies/vibe-mcp

How to install

What it does

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

  • Connects Computer or cloud
  • Account or key No key needed
  • Category Web & browsers

Use together with

Skills that teach the AI this kind of work; they work alongside this one

timesfm

TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.

by google-research★ 35,6291 skills

Skill · How-to guide

Shadowbroker

Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…

by BigBodyCobain★ 11,6021 skills

Skill · How-to guide

google-maps-scraper

scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place

by gosom★ 8,2091 skills

Skill · How-to guide

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity7/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score19/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install Vibe MCP — Real Chrome, Remotely. Follow https://mcp.popnx.com/i/vibetechnologies-vibe-mcp.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · What you ask goes through the maker’s server (relay.api.vibebrowser.app) · ✓ Commands checked Nov 13, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

The address has {…} parts you must replace with your own first · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it

  1. Open Claude’s Connectors page

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. Click “Add” → “Custom” → “Web” and fill in these 2 fields

    Copy each value into the field with the same name in Claude, then click Continue

    Name · NameVibe MCP — Real Chrome, Remotely
    Remote MCP server URL · Addresshttps://relay.api.vibebrowser.app/mcp/{session_id}

    Click Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add

  3. Turn it on in a chat

    +ConnectorsVibe MCP — Real Chrome, Remotely

  4. Try it

    Use Vibe MCP — Real Chrome, Remotely and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Vibe MCP — Real Chrome, Remotely or shows a Vibe MCP — Real Chrome, Remotely tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with ChatGPT, depending on your plan

Full MCP: ChatGPT Business, Enterprise or Edu on the web · Pro: connects with read/fetch permissions, so tools that change data may not work · Plus: not confirmed in OpenAI’s docs; if you see an add-custom-MCP option on the Plugins page you can try these steps · web only · The address has {…} parts you must replace with your own first

  1. Open ChatGPT’s add-MCP page on the web

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. Fill in the name and address

    Enter a name, paste the address under Connection, tick the risk warning and click Create as a plugin

    Name · NameVibe MCP — Real Chrome, Remotely
    Connection · Addresshttps://relay.api.vibebrowser.app/mcp/{session_id}
  3. Pick Vibe MCP — Real Chrome, Remotely in a chat

    Start a new chat and pick Vibe MCP — Real Chrome, Remotely from your plugins before typing

  4. Try it

    Use Vibe MCP — Real Chrome, Remotely and tell me what you can do for me, then show me one thing

    ✓ If ChatGPT says it is using Vibe MCP — Real Chrome, Remotely or shows a Vibe MCP — Real Chrome, Remotely tool in the answer, you are connected

Menu names checked against OpenAI’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Claude Code, with some setup first

The address has {…} parts you must replace with your own first

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  2. Paste this command and press Enter

    claude mcp add --transport http --scope user vibe 'https://relay.api.vibebrowser.app/mcp/{session_id}'
  3. Type /mcp in Claude Code

    You should see Vibe MCP — Real Chrome, Remotely listed as connected

  4. Try it

    Use Vibe MCP — Real Chrome, Remotely and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Vibe MCP — Real Chrome, Remotely or shows a Vibe MCP — Real Chrome, Remotely tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

The address has {…} parts you must replace with your own first

  1. Open Cursor’s MCP settings file

    ~/.cursor/mcp.json

    Paste these settings, fill in the empty values and save

    {
      "mcpServers": {
        "vibe": {
          "url": "https://relay.api.vibebrowser.app/mcp/{session_id}"
        }
      }
    }
  2. Open the AI chat in Cursor in Agent mode

  3. Try it

    Use Vibe MCP — Real Chrome, Remotely and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Vibe MCP — Real Chrome, Remotely or shows a Vibe MCP — Real Chrome, Remotely tool in the answer, you are connected

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

The address has {…} parts you must replace with your own first

  1. Open VS Code’s MCP settings file

    MCP: Open User Configuration

    Paste these settings, fill in the empty values and save

    {
      "servers": {
        "vibe": {
          "type": "http",
          "url": "https://relay.api.vibebrowser.app/mcp/{session_id}"
        }
      }
    }
  2. Open the AI chat in VS Code in Agent mode

  3. Try it

    Use Vibe MCP — Real Chrome, Remotely and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Vibe MCP — Real Chrome, Remotely or shows a Vibe MCP — Real Chrome, Remotely tool in the answer, you are connected

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

Address for apps that connect over the web

Addresshttps://relay.api.vibebrowser.app/mcp/{session_id}

JSON settings are under “For developers” below

Stuck? Ask people who use Vibe MCP — Real Chrome, Remotely💬 Discussion →
For developers: Terminal commands and JSON settings

Over the web

Claude Code

claude mcp add --transport http --scope user vibe 'https://relay.api.vibebrowser.app/mcp/{session_id}'

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "vibe": {
      "url": "https://relay.api.vibebrowser.app/mcp/{session_id}"
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "vibe": {
      "type": "http",
      "url": "https://relay.api.vibebrowser.app/mcp/{session_id}"
    }
  }
}

Installed on your computer

Claude Code

claude mcp add --scope user vibe -- npx -y @vibebrowser/mcp

Claude Desktop (claude_desktop_config.json)

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

Cursor (~/.cursor/mcp.json)

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

VS Code (mcp.json)

{
  "servers": {
    "vibe": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@vibebrowser/mcp"
      ]
    }
  }
}

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
157/wk
Licencei
Apache-2.0
Connection
Computer or cloud
Transport
stdio, streamable-http
Latest versioni
0.3.6
Published to registryi
Aug 21, 2026
Code last changedi
Nov 6, 2026
Last checked
Nov 19, 2026
Maker
VibeTechnologies
Packages
npm: @vibebrowser/mcp
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Connect over the internet in

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

The address needs your own values, so we cannot read the tool list for you.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account VibeTechnologies, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 13 days ago

  • ✓ Pass

    Has a licence

    Uses Apache-2.0

  • – Not applicable

    Endpoint responds

    The address needs your own account values, so we cannot check it for you

  • – Not applicable

    Sign-in with OAuth

    The address needs your own account values, so we cannot check it for you

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for @vibebrowser/mcp@0.3.6

Checks only this package version, not every dependency · checked Nov 15, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/vibetechnologies-vibe-mcp.svg)](https://mcp.popnx.com/en/servers/vibetechnologies-vibe-mcp)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Web & browsersi

  • More stars than 86% of the other 1613 servers in this category
  • Published to the registry more recently than 20% of the other 1613 servers in this category
  • Basic checks equal to or better than 99% of the other 1613 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Vibe MCP — Real Chrome, Remotely safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed 13 days ago, and the latest version (0.3.6) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).

What can I use instead?

In the same category: Browser Use, changedetection.io (official), Apify MCP Server, Pomerado, Actionbook

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Browser Use

Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.

by browser-useWidely used↓ 1.7M/wk★ 121.4KUpdated 29 days ago

Computer or cloud✓ service owner · browser-use.com

Apify MCP Server

Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡

by apifyWidely used★ 16.9KUpdated 2 days ago

Runs in the cloud✓ service owner · apify.com

Pomerado

Connect your agents to any website. The cheaper, faster and more reliable alternative to browser use

by PomeradoGrowing★ 1.8KUpdated yesterday

Runs in the cloud✓ service owner · pomerado.ai

Actionbook

Let your AI agent operate any website through a real, logged-in browser session.

by actionbookGrowing★ 1.6KUpdated 31 days ago

Runs in the cloud✓ service owner · actionbook.app
Compared with similar ones
This one
Vibe MCP — Real Chrome, Remotely
Browser Usechangedetection.io (official)Apify MCP ServerPomeradoActionbook
Runs whereCloud or install on your computerCloud or install on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyNoYesNoYesNoNo
Add with + in ClaudeNoYesNoNoNoNo
Basic checks3/35/53/34/44/44/4
LicenseApache-2.0MITApache-2.0MITMITApache-2.0
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Vibe MCP - Browser Automation for AI Agents

MCP server for Vibe AI Browser — drive your real, logged-in Chrome from any MCP client, including agents running on a different machine with no inbound port open.

⚠️ Security — treat your relay URL/UUID like a password. A relay URL or extension UUID (wss://relay.api.vibebrowser.app/ ) grants live control of your browser session (read your tabs, take screenshots, read page content). Never share it, paste it into a chat with untrusted parties, or commit it to a repo. Every example UUID in this documentation is a non-routable placeholder (YOUR-EXTENSION-UUID or 00000000-0000-0000-0000-000000000000) — substitute your own secret value locally and keep it out of version control.

Privacy

Privacy policy: https://vibebrowser.app/privacy — what the extension, the local MCP server, and the hosted relay collect, log, and retain, including the relay's security audit records and how to revoke a connection URL.

Install prompt for AI agents (OpenClaw / Hermes)

Paste the block below into your OpenClaw or Hermes agent. Replace the last line with your remote value — the connector URL (https://relay.api.vibebrowser.app/mcp/ ) shown in the Vibe extension's Settings → AI Agent Control → Remote (internet) → Relay access (a bare UUID or a wss:// relay URL also still work). That's the only edit you make.

You are setting yourself up to control my real Chrome through Vibe Browser. Work through the steps in order, and after each step confirm it worked before moving on. Do not claim a step is done until you have proven it.
  1. Install the "vibebrowser" skill for your runtime:
  • OpenClaw: npx -y skills add VibeTechnologies/vibe-mcp -s vibebrowser -a openclaw -g -y --copy --dangerously-accept-openclaw-risks then run openclaw skills list and confirm a "vibebrowser" row shows "ready" as installer registration.
  • Hermes: npx -y skills add VibeTechnologies/vibe-mcp -s vibebrowser -y optional installer registration check: npx -y skills list shows a "vibebrowser" row.
  1. Remember my remote so I only give it to you once. Save it to a file vibebrowser-cli.md in your persistent agent workspace root (the directory that holds your memory/ folder — not the shell's working dir, not $HOME unless they are the same) as a line remote: ; if your runtime can also write memory keys, additionally store it under vibebrowser_remote. On every later command — including the first message of a new conversation — load it back from that file and reuse it without asking me again.
  1. Record a standing rule so you route correctly later: whenever I ask you to do anything in MY browser / MY Chrome / MY tabs / the page I'm on, use this vibebrowser skill (npx -y @vibebrowser/cli@latest with my saved remote) to drive my REAL browser — never your built-in, headless, or in-pod browser, never web-fetch instead, and never run vibebrowser. Save this rule wherever your standing instructions/memory live so it applies in future conversations.
  1. Confirm you can control my Chrome, retrying on "Extension reconnecting" (wait 3s, up to 5x): npx -y @vibebrowser/cli@latest --remote " " --json status --wait-for-extension --wait-timeout 20000 npx -y @vibebrowser/cli@latest --remote " " --json snapshot --format aria

Then report: (1) is extensionConnected true, (2) did the snapshot return my real page content?

My remote:

Why Vibe MCP?

The browser-automation MCP space moved fast. Most of what used to differentiate us is now table stakes — so here is an honest scorecard. Where a competitor matches us, the column says Yes.

CapabilityVibe MCPPlaywright MCPChrome DevTools MCPClaude for ChromeBrowserMCP
Uses your real profile / logged-in sessionsYesYes (--extension)Yes (own --user-data-dir)YesYes
No per-connection approval dialogYesYes (token)Yes (dedicated profile only)YesYes
**Real logged-in profile *and* no dialog, together**YesYesNo — pick oneYesYes
Multiple agents against one browserYesYes (--shared-browser-context)Yes (--experimentalPageIdRouting)NoNo
Agent on another machine, no inbound portYes — extension dials out to a relayNoNo — needs an inbound debug port + forwardingNoNo
Works with any MCP client (Codex, OpenCode, Cursor, Hermes, OpenClaw)YesYesYesNo — Anthropic surfaces onlyYes

Two rows are ours alone:

  • Outbound, cross-machine control. The Vibe extension opens an outbound WebSocket to a relay (wss://relay.api.vibebrowser.app/ ). Nothing listens on the user's machine, nothing is port-forwarded, and the agent can live in a pod, a cron job, or a chat bot. No competitor documents an extension-initiated outbound connection to a remote MCP server.
  • Real profile without the dialog tax. Chrome DevTools MCP needs approval for *each* WebSocket connection to Chrome (#1794, open; persistence was closed won't-fix). The maintainer's workaround — --remote-debugging-port with a dedicated --user-data-dir — avoids the dialog by giving up your logged-in profile. So: skip the dialog, or use your real profile — not both.

Also worth knowing:

  • Vendor lock-in. Claude for Chrome is GA, clicks and types via the debugger permission, and supports scheduled tasks — it is the closest competitor. But it only drives Anthropic's own surfaces (side panel, Claude Desktop connector, Cowork, Claude Code). There is no public API or MCP surface, so Codex, OpenCode, Hermes and OpenClaw cannot use it. Vibe MCP is agent-agnostic.
  • Stability. Chrome DevTools MCP is explicitly experimental and currently carries open memory-leak (#2431, #2291, #2456) and concurrency (#1763, #1921) issues.
Multi-Agent Architecture

Run Claude Desktop, Cursor, VS Code Copilot, and OpenCode at once — they share control of one browser through the relay, which multiplexes requests and routes each response back to the agent that asked.

Claude Desktop       Cursor          VS Code         OpenCode

| | | | v v v v [vibebrowser-mcp] [vibebrowser-mcp] [vibebrowser-mcp] [vibebrowser-mcp] | | | | +------------------+----------------+---------------+ | v [Relay Daemon] <-- Auto-spawned, handles multiplexing | v [Vibe Extension] | v [Your Chrome]

Features

  • Multi-Agent Ready - Run Claude, Cursor, VS Code, and more simultaneously against one browser
  • Uses Your Browser - No separate browser instance, uses your existing Chrome with all your logins
  • Remote-capable - The extension dials out to a relay, so the agent can run on another machine with no inbound port
  • Local by default - In local mode everything stays on 127.0.0.1; only remote relay mode routes traffic through relay.api.vibebrowser.app
  • Direct Chrome DevTools mode - Extension tools stay primary by default; use --devtools to drive your real running Chrome directly over the DevTools Protocol (no extension required)

Quick Start

1. Install the Vibe Extension

Install the Vibe AI Browser extension in Chrome, Brave, or any Chromium browser:

Option A: Chrome Web Store (Recommended)

  1. Visit the Chrome Web Store
  2. Click "Add to Chrome"
  3. The Vibe icon will appear in your toolbar

Option B: Developer Version

  1. Download the latest release ZIP
  2. Extract to a permanent folder
  3. Go to chrome://extensions, enable Developer Mode
  4. Click "Load unpacked" and select the extracted folder

For detailed instructions, see the installation guide.

2. Configure Your AI Application

Claude Desktop

Edit your Claude Desktop config file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
{

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

Restart Claude Desktop after saving.

Cursor

  1. Open Cursor Settings (Cmd/Ctrl + ,)
  2. Go to "Features" -> "MCP Servers"
  3. Click "Add Server" and add:
{

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

Or edit ~/.cursor/mcp.json directly.

VS Code (GitHub Copilot)

Add to your VS Code settings.json:

{

"github.copilot.chat.mcpServers": { "vibe": { "command": "npx", "args": ["-y", "@vibebrowser/mcp"] } } }

Windsurf

Edit ~/.codeium/windsurf/mcp_config.json:

{

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

OpenCode

Add to your .opencode/config.json:

{

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

Gemini CLI

Add to ~/.gemini/settings.json:

{

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

OpenAI Codex CLI / ChatGPT desktop app / Codex IDE extension

All three share one config file: ~/.codex/config.toml. Configure once, use everywhere.

Easiest — let Codex write the entry:

codex mcp add vibe -- npx -y @vibebrowser/mcp

Or add the table to ~/.codex/config.toml by hand (Codex uses TOML, not JSON):

[mcp_servers.vibe]

command = "npx" args = ["-y", "@vibebrowser/mcp"]

In the ChatGPT desktop app you can also use the UI: Settings → MCP servers → Add server, choose STDIO, command npx, args -y @vibebrowser/mcp, then Restart.

Verify with codex mcp list, or type /mcp in the Codex

Only the beginning is shown; read the rest in the repo