Ridealong

Name: Ridealong
Author: williamblaismedia-create

作者：williamblaismedia-create版本 0.1.0i★ –i在你的电脑上运行

注册名称io.github.williamblaismedia-create/ridealong

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 网页与浏览器

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： RIDEALONG_DATA_DIR, RIDEALONG_LIVE_PORT, RIDEALONG_VIDEO

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "ridealong": {
      "command": "npx",
      "args": [
        "-y",
        "ridealong-mcp"
      ],
      "env": {
        "RIDEALONG_DATA_DIR": "your-value",
        "RIDEALONG_LIVE_PORT": "your-value",
        "RIDEALONG_VIDEO": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add ridealong --env RIDEALONG_DATA_DIR=your-value --env RIDEALONG_LIVE_PORT=your-value --env RIDEALONG_VIDEO=your-value -- npx -y ridealong-mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "ridealong": {
      "command": "npx",
      "args": [
        "-y",
        "ridealong-mcp"
      ],
      "env": {
        "RIDEALONG_DATA_DIR": "your-value",
        "RIDEALONG_LIVE_PORT": "your-value",
        "RIDEALONG_VIDEO": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "ridealong": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "ridealong-mcp"
      ],
      "env": {
        "RIDEALONG_DATA_DIR": "your-value",
        "RIDEALONG_LIVE_PORT": "your-value",
        "RIDEALONG_VIDEO": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

RIDEALONG_DATA_DIR env
Profile, secret and artifacts directory (default ~/ridealong-data)
RIDEALONG_LIVE_PORT env
Live view port (default 9400)
RIDEALONG_VIDEO env
on/off — H.264 live stream via ffmpeg (default on)

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 williamblaismedia-create 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“网页与浏览器”中的其他服务器比较i

星标数多于此分类中其他 881 个服务器的 0%
发布到注册中心的时间比此分类中其他 881 个服务器的 39% 更新
基础检查结果等于或优于此分类中其他 881 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Ridealong 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.1.0）于2个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Browser Use, Chrome DevTools MCP, MCP Server Browser

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Browser Use

作者：browser-use

Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.

电脑或云端★ 120,087MIT17天前更新

安装

Chrome DevTools MCP

作者：ChromeDevTools

MCP server for Chrome DevTools

在你的电脑上运行★ 54,821Apache-2.016天前更新

安装

MCP Server Browser

作者：bytedance

MCP server for browser use access

在你的电脑上运行★ 39,550Apache-2.014个月前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

RIDEALONG

A browser your AI drives. Ride along, grab the wheel anytime.

MCP server for Claude Code · real Google Chrome · live H.264 view · human-in-the-loop by design

Website · Quick start · Site en français · README en français

Every browser MCP lets an agent click around in the dark. Ridealong puts you in the passenger seat. Claude drives a real Chrome; you open one link and see exactly what it sees, where it clicks, what it typed — and when it hits a login, a CAPTCHA or a payment, you take the wheel from your phone, then hand it back.

In Claude Code

Ridealong is an MCP server: Claude calls its tools like any other, but every step is visible on the live view, William's pointer and messages come back into the transcript, and sensitive actions wait for an approval.

On your phone

Not just another browser MCP

Why Ridealong

	Typical browser MCP	Ridealong
Browser	headless Chromium	real Google Chrome (codecs, extensions, your profile)
Watch the agent	screenshots on request	live stream, GPU-encoded H.264, ~150 ms behind
Intervene	stop the run	Manual mode: your clicks, keys and scroll go straight into the page
Sensitive actions	hope	`ask_approval`: Approve / Deny on your phone, the tool waits
Guide the agent	type a long prompt	tap the element on the live view, or send a one-line message
Secrets	in the transcript	never: Manual input is not stored, logged, or visible to Claude
Session dies	reconnect by hand	self-healing relay + zombie-proof live view

Quick start

On the machine Claude drives — nothing to host:

claude mcp add ridealong -- npx -y -p ridealong-mcp ridealong

Or as a Claude Code plugin: claude plugin marketplace add williamblaismedia-create/ridealong then claude plugin install ridealong@ridealong. From source: git clone … && npm ci && npm run build && claude mcp add ridealong -- "$PWD/scripts/ridealong-local.sh".

Then, in Claude Code: *"open timeliner.io and give me the live view"*. You get a signed link (http://127.0.0.1:9400/#token=…). Open it once on a device and the bare address works for 30 days — bookmark it.

In Docker (Chrome under Xvfb, ffmpeg, persistent profile):

docker build -t ridealong . && claude mcp add ridealong -- docker run -i --rm -p 9400:9400 -v ridealong-data:/data ridealong

On an always-on server with an NVIDIA GPU, a Cloudflare tunnel and a relay that survives your laptop sleeping: the reference setup is in docs/DEPLOIEMENT-W-AGENT.md (French).

ffmpeg installed → H.264 video (NVENC · VideoToolbox · libx264, auto-detected). No ffmpeg → JPEG frames. Either way it works.

Examples

Three copy-pasteable scenarios in examples/, each with the exact prompt, what you see on the live view and where you step in:

QA after deploy — reload with the cache bypassed, click through the flow, read console_errors and network_requests, report. Includes a CLAUDE.md snippet to run it after every deploy.
Approval-gated purchase — Claude fills the checkout, ask_approval blocks before "Place order", you tap Approve on your phone.
Login handoff — Claude hits a login or 2FA wall, switches to Manual, you type on your own device, Claude never sees the keystrokes.

What you get on the live view

Claude's cursor gliding to each target, a ripple on click, the action label — and a journal with timestamps.
Auto | Manual toggle. In Manual, mouse, keyboard, trackpad scroll and pinch are relayed; Claude's perception is suspended while you type.
Pause Claude without taking control.
Approval cards when Claude calls ask_approval.
Point at things (Auto mode tap → *"William points at: button « Login »"*) and message Claude from the page. They reach Claude at the end of his next tool result — or instantly, as a Claude Code channel, if you start Claude with --dangerously-load-development-channels server:ridealong (also relays "took the wheel" / "paused").
Real tabs: the strip mirrors Chrome; tap one to move Claude's target.
Resolution picker (720p → 2K), applied live and remembered.
Capture, fullscreen, video/JPEG switch, reconnects by itself, phone-ready.

Tools

Perceive	Act	Tabs	Live view
`state` `snapshot` `find` `read`	`navigate` `reload` `act` `fill` `scroll`	`tabs_list` `tabs_open` `tabs_select` `tabs_close`	`live_start` `live_mode` `live_stop`
`diff` `screenshot` `console_errors`			`ask_approval` `inbox`
`network_requests` `fetch_with_session`

Everything follows one target tab. Elements carry stable [ref]s from snapshot/find, so Claude acts by reference, never by brittle selectors. Chrome's HTTP cache and service workers are bypassed: a site you just deployed is what Claude sees.

How it works

Claude Code ──stdio──▶ ridealong (MCP) ──CDP──▶ Google Chrome

│ └─ live view ── ws ──▶ your browser / phone JPEG frames, or CDP screencast → ffmpeg (GPU) → fMP4 → MSE input relay ◀── Manual mode (never stored)

Two Claude Code sessions on one Chrome? The second follows the first as a control client and promotes itself if the first goes away. A local relay (scripts/ridealong-mcp-relay.mjs) keeps the MCP session alive across a dead SSH link by replaying the handshake.

Guarantees

No capture. Manual-mode input is relayed straight to Chrome and never retained; perception tools refuse to run while you have control; password fields never expose values in snapshots. A test suite pins this down.
Signed, expiring links (HMAC, 30 s – 1 h). Device tokens (30 days) live only in your browser. Rotate RIDEALONG_LIVE_SECRET to revoke everything.
Loopback by default. The live view listens on 127.0.0.1; you choose how to expose it.

Roadmap

Session recording (video + journal as chapters)
Adaptive bitrate for weak mobile links
Profiles: one Chrome context per client / task, incognito
Annotated screenshots (refs drawn on the image)
npx ridealong-mcp

Contributing

Issues and PRs welcome — see CONTRIBUTING.md. npm test runs 131 tests against a real Chromium (and ffmpeg when present).

Built by W Automatisations · Montréal · MIT