MCP.Market

Vibe MCP — Real Chrome, Remotely MCP server

by VibeTechnologies·io.github.VibeTechnologies/vibe-mcp·v0.3.6·3 stars
No reviews yet

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

B72/100grade B
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
B72/100

full report

Adoption
Growing

3 stars168 downloads/wk

Reviews

Write one

Nobody has reviewed Vibe MCP — Real Chrome, Remotely yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Vibe MCP — Real Chrome, Remotely tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-11-02 · same rubric, same numbers if you re-run it

1 high1 medium
  • Code scan50 source files scanned8/25
  • Live reliabilityremote reachable in 557ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityauth enforced (unknown)9/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10

Findings (2)

  • highcurl | sh in a scriptinstall.curl-pipe
    dist/ollama.js: … } else { execSync('curl -fsSL https://ollama.com/install.sh | sh', { stdio: 'inherit' }); } …
  • mediumeval / new Function usedexec.eval
    dist/tool-annotations.js: … JavaScript expression through `new Function()` in the * page.…
Overall 72/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Vibe MCP — Real Chrome, Remotely compares

Against every graded Productivity MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
72/100
higher than 35% of 1,297 Productivity servers
GitHub stars
3
more than 65% of 852 Productivity servers
Downloads a week
168
more than 68% of 423 Productivity servers with a package

Install Vibe MCP — Real Chrome, Remotely in Claude Code, Cursor or VS Code

claude mcp add --transport http vibe-mcp https://relay.api.vibebrowser.app/mcp/{session_id}
Add to Cursor

What the publisher says

From the Vibe MCP — Real Chrome, Remotely repository's README, as published. We do not edit it. Read it on GitHub

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.

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.

2. 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: <value>`; 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

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.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Grade history

  • 2026-11-02restoreC → Bscore 72: curl | sh in a script; eval / new Function used

Vibe MCP — Real Chrome, Remotely: common questions

Is Vibe MCP — Real Chrome, Remotely MCP server safe?
Mostly: it is graded B (72/100). Read the Vibe MCP — Real Chrome, Remotely safety report
How do I install Vibe MCP — Real Chrome, Remotely?
It runs remotely at relay.api.vibebrowser.app. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Vibe MCP — Real Chrome, Remotely need an API key?
Yes. The endpoint refuses requests without credentials; the publisher's docs say how to get them.
Is Vibe MCP — Real Chrome, Remotely maintained?
The last commit was in the last day (2026-11-01). The latest release is v0.3.6.
What can I use instead of Vibe MCP — Real Chrome, Remotely?
Servers from other publishers that do the same job: Agent Webbridge MCP server, INSSIST MCP server and DOMShell MCP server. Compare all Vibe MCP — Real Chrome, Remotely alternatives.
How does Vibe MCP — Real Chrome, Remotely compare with other Productivity MCP servers?
safety score 72/100 (higher than 35% of 1,297 Productivity servers); github stars 3 (more than 65% of 852 Productivity servers); downloads a week 168 (more than 68% of 423 Productivity servers with a package). Full comparison.

Alternatives to Vibe MCP — Real Chrome, Remotely

Same job from other publishers: the closest match first, then the best rated.

All Vibe MCP — Real Chrome, Remotely alternatives →
  • Agent Webbridge
    Drive your real, logged-in Chrome (many profiles, parallel tabs) from any MCP client. Local only.
    A
  • INSSIST
    Drive your own logged-in Instagram session via the INSSIST extension: read, publish, DMs, analytics.
    A
  • DOMShell
    Drive Chrome with filesystem commands (ls, cd, grep, click, type). One MCP tool, multi-agent.
    A
  • Argent
    Drive iOS Simulators, Android emulators, TVs and Electron/web apps from your coding agent
    A
  • gflow-cli
    Drive Google Flow from an agent: Veo video and Imagen image generation
    A