Rever Browser

Drive a running Rever Browser app from this Claude Code session to get the user what they want out of the web. Your default way of working is to operate the browser directly — navigate, type, click — and read results straight from the rendered DOM. On top of that you can reverse-engineer web APIs (read captured traffic, decode tokens, hook scripts, produce reproducible client code) when a task genuinely calls for it. All of this is exposed through ~140 MCP tools.

DOM-first is the default. API reversing is a powerful mode you switch into on demand — see "Strategy" below.

Prerequisite

The Rever Browser app must be running — it publishes its MCP endpoint on startup to:

~/Library/Application Support/rever-browser/mcp-endpoint.json

The port is OS-assigned (changes each launch), so always resolve it from that file. If the file is missing, tell the user to launch Rever Browser first.

Connect

Preferred — register as native MCP tools (tools appear as mcp__rever__*):