Vibe MCP - Real Chrome, Remotely

Drive your real, logged-in Chrome from any MCP client - even from a remote machine, no inbound port. Its 7 documented tools cluster into navigate, click, scroll, take.

People connecting browser automation tools to Claude, Cursor, VS Code, or another MCP client. The project is written in JavaScript.

VERIFIED ACTIVE

LAST COMMIT 2026-08-23 · ★ 2 · #65 OF 196 MAINTAINED BROWSER AUTOMATION · VERIFIED 2026-08-25

Apache-2.0 · JavaScript servers · how we verify → /methodology

01 · Install Vibe MCP - Real Chrome, Remotely

before you install - you'll need

Set VIBE_REMOTE_URL, PUBLIC_MCP_URL before connecting.

Claude Code

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

Claude Desktop / Cursor / VS Code - add to config

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

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

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

transport: streamable-http

endpoint alive - authentication required · probed 2026-08-25

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions · remote - your agent's requests go to relay.api.vibebrowser.app

endpoint auth requires authentication - rejected our unauthenticated MCP initialize

license Apache-2.0 - declared in the repository

npm package @vibebrowser/mcp - the @vibebrowser scope differs from the repo owner (vibetechnologies); confirm it's the project's official package

registry namespace io.github.VibeTechnologies is GitHub-verified and matches the repo owner

03 · What Vibe MCP - Real Chrome, Remotely can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

What you can build

With this server connected, an agent can navigate to any URL, click elements on the page, capture screenshots, and extract page text/HTML.

Capability map

Tools grouped from the project's README - what Vibe MCP - Real Chrome, Remotely lets an agent do.

Navigate

1 tool - e.g. Navigate to any URL

navigate_to_url

Click

1 tool - e.g. Click elements on the page

click

Scroll

1 tool - e.g. Scroll the page

scroll

Take

1 tool - e.g. Capture screenshots

take_screenshot

read & search

1 tool - e.g. Extract page text/HTML

get_page_content

Keyboard

1 tool - e.g. Press keyboard combinations

keyboard_shortcut

Web

1 tool - e.g. Search the web

web_search

Latest releases

v0.2.12 · 2026-06-16

What's new in v0.2.12 · Real Chrome over CDP (--devtools mode) · Drive your actual Chrome browser directly over CDP without the extension relay, via the chrome-use core (#75) · Per-profile gateway socket - a proxy…

04 · Who maintains Vibe MCP - Real Chrome, Remotely

Vibe MCP - Real Chrome, Remotely is maintained by vibetechnologies. It's the only MCP server we track from this author; the repo dates to Jan 2026.

05 · Facts

repository: github.com/vibetechnologies/vibe-mcp
website: https://vibebrowser.app/
category: browser automation - ranked #65 of 196 actively-maintained browser automation servers as of 2026-08-25.
release cadence: 1 release in the last 90 days (latest 2026-06-16)
registry: io.github.VibeTechnologies/vibe-mcp (active, first published 2026-08-07 · 5 versions)
packages: npm:@vibebrowser/mcp

06 · Vibe MCP - Real Chrome, Remotely FAQ

Is Vibe MCP - Real Chrome, Remotely still maintained?

Yes - as of 2026-08-25, its last commit was 2026-08-23 and it shipped 1 release in the last 90 days. We re-verify nightly.

What can Vibe MCP - Real Chrome, Remotely do?

With this server connected, an agent can navigate to any URL, click elements on the page, capture screenshots, and extract page text/HTML.

How do I install Vibe MCP - Real Chrome, Remotely?

Run `npx -y @vibebrowser/mcp`. The README documents 2 environment variables (VIBE_REMOTE_URL, PUBLIC_MCP_URL) to set first. Set VIBE_REMOTE_URL, PUBLIC_MCP_URL before connecting. You can also paste the ready-made client config above.

Does Vibe MCP - Real Chrome, Remotely require authentication?

Yes - when we probed the endpoint on 2026-08-25, it rejected an unauthenticated MCP initialize; you'll need credentials to connect.

07 · Alternatives to Vibe MCP - Real Chrome, Remotely

Alternatives to Vibe MCP - Real Chrome, Remotely

Maintained browser automation servers if Vibe MCP - Real Chrome, Remotely isn't the fit.

Pairs well with

Servers that cover what Vibe MCP - Real Chrome, Remotely doesn't - only shown when the pairing reason fits the companion.

More browser automation MCP servers · AndroJack MCP · Devloop · Nestegg Calculators · Jshookmcp · Webdriverio MCP Server

More JavaScript MCP servers · Visily UI Design · Thunderbird CLI · Vynly MCP · VULK · see all