Vibe MCP — Real Chrome, Remotely MCP Server

by vibetechnologies Your server? Claim it

answering

Vibe MCP — Real Chrome, Remotely is answering right now. Last checked 9 min ago. 237 installs a week from npm. Last commit 23 Aug 2026.

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

Installs per day peak 202 · avg 50 · -59% w/w

a month agotoday

Uptime history 24 days of history · worst day 33%

24 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

213 ms

Response time

average over 24h

237

Installs / week

npm and PyPI

What the code does

We read the source, 11 h ago · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs an external command .claude/hooks/task-readiness-check.cjs:28, mcpb/build.mjs:37, src/chrome-use/proxy-launcher.ts:71 и ещё 4

    const proc = spawn(CLAUDE, args, {

Builds a file path from a variable mcpb/build.mjs:62

const tarballPath = path.join(packDir, tarballName);

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

[mcp_servers.vibe-mcp]
url = "https://relay.api.vibebrowser.app/mcp/{session_id}"

.cursor/mcp.json

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

.vscode/mcp.json

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

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URL	Transport	State	Latency	Checked
https://relay.api.vibebrowser.app/mcp/{session_id}	streamable-http	needs key	251 ms	9 min ago

Alternatives to Vibe MCP — Real Chrome, Remotely

same job, measured the same way

Doppel

by samrj12

Drive your real, logged-in Chrome/Edge from AI agents over CDP. Faster. Sharper.

155 installs/wk local only

Chrome Bridge

by frsorrentino

Your real, logged-in Chrome as an MCP server: 63 token-efficient web-dev tools. ChromeOS included.

77 installs/wk local only

Agent360 Browser MCP

by agent360dk

Give AI agents control of your real, logged-in Chrome. Chrome extension + MCP server, 34 tools.

477 installs/wk local only

Tap

by leonting1010

Browser MCP for logged-in tasks. Uses your Chrome — credentials stay local. Zero-token replay.

746 installs/wk 4 tools answering

Google CrUX MCP

by a1-x-tech

Real-user Core Web Vitals from the Chrome UX Report (CrUX) API for any origin or URL.

136 installs/wk local only

WebLoom

by webloomhq

86 tools: drive YOUR real Chrome via CDP + browse/install/publish Threads in chat. webloom.run.

local only

Chromeflow

by chromeflow

Lets Claude Code or Codex CLI drive your real Chrome — sessions intact, 28 browser tools.

local only

Chromeflow

by neodrew

Lets Claude Code or Codex CLI drive your real Chrome — sessions intact, 28 browser tools.

local only

Vibe MCP — Real Chrome, Remotely — questions

Answers built from our own checks of this server.

Why is there no tool list for Vibe MCP — Real Chrome, Remotely?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Vibe MCP — Real Chrome, Remotely working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 213 ms. The bar chart above shows every period we have measured.

How do I connect Vibe MCP — Real Chrome, Remotely?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key or an OAuth login: it refuses anonymous clients.

Does Vibe MCP — Real Chrome, Remotely need an API key?

Yes. Every time we knock, Vibe MCP — Real Chrome, Remotely answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is Vibe MCP — Real Chrome, Remotely?

It answers our handshake in 213 ms on average, which is faster than 70% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use Vibe MCP — Real Chrome, Remotely?

The npm package @vibebrowser/mcp was installed 237 times in the last week. Week over week that is -59%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is Vibe MCP — Real Chrome, Remotely open source?

Yes — it is published under the Apache-2.0 licence, written in JavaScript, 3 stars on GitHub and 10 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.