mcpbeat Sign in

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 8 min ago. 261 installs a week from npm. Last commit 30 Sep 2026.

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

Installs per day peak 104 · avg 39 · -1% w/w
a month agotoday
Uptime history 69 days of history · worst day 33%
69 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
239 ms
Response time
average over 24h
261
Installs / week
npm and PyPI

What the code does

We read the source, 10 d ago · rules ccca72095570

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.

Three servers free · no card

Connect this server

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

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 from its owner to call it.

Endpoints

URLTransportStateLatencyChecked
https://relay.api.vibebrowser.app/mcp/{session_id} streamable-http needs key 279 ms 8 min ago

Alternatives to Vibe MCP — Real Chrome, Remotely

same job, measured the same way
Agent Webbridge
by jeet-dhandha

Drive your real, logged-in Chrome (many profiles, parallel tabs) from any MCP client. Local only.

802 installs/wk local only
Agent360 Browser MCP
by agent360dk

Drive your real, logged-in Chrome from any AI agent - 40 tools. Needs our Chrome extension too.

1 828 installs/wk local only
Claw Post
by daydreamnationtechlabs

Agent social posting via your logged-in Chrome. Remote MCP + OAuth. Not clawpost.dev.

answering
D
Doppel
by samrj12

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

44 installs/wk local only
Usable Browser Agent
by savvy-tech-sphere

MCP server and Firefox add-on that let an AI agent drive your real, logged-in browser. Free tier.

32 installs/wk local only
Ridealong
by williamblaismedia-create

Watch your AI drive a real Chrome live, point, approve, or take the wheel from your phone.

28 installs/wk local only
Caishi
by zhongquinnking

Read Bilibili, Douyin, Xiaohongshu and any web page via your own logged-in Chrome.

444 installs/wk local only
chrome-mcp
by mehmoodqureshi

Drive your real Chrome over MCP: real logins and cookies, multi-tab automation, deny-all by default.

1 611 installs/wk 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 92 of 92 checks got a reply (100.0%), average response time 239 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: 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 239 ms on average, which is faster than 54% 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 261 times in the last week. Week over week that is -1%. 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 11 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.