Now with MCP — drive it from Claude Code & Cursor

See, intercept, and edit your HTTP traffic.
Built for humans and AI agents.

Reversee is an open-source reverse-proxy web debugger. Point your client at it and inspect every request and response — headers, bodies, timings — then rewrite or breakpoint them on the fly. And let AI agents do it too, over MCP.

Download for macOS, Windows, Linux View on GitHub ↗
Reversee inspecting HTTP traffic: a table of requests with methods, status codes and content types, and a JSON response body in the detail pane.

Everything you need to debug traffic

A focused, modern UI over a proxy that gets out of your way.

HTTP & HTTPS

Listen and forward on either protocol. HTTPS uses a locally generated root CA you trust once.

Traffic inspection

Method, path, status, content type, headers, request/response bodies (syntax-highlighted), and timings.

Interceptors

Rewrite requests or responses with a few lines of JavaScript — change headers, bodies, anything.

Breakpoints

Hold requests matching a URL pattern, edit the URL, headers, and body, then continue.

gRPC

Proxy native gRPC over HTTP/2 and decode every message — unary and streaming — into readable JSON from your .proto/.desc.

Redirect & host rewriting

Keep redirect chains and Host headers pointed back at the proxy so flows just work.

Copy as curl & export

Reproduce any captured request as a curl command, and export diagnostics in a click.

Debug gRPC, decoded

Turn on gRPC and Reversee runs an HTTP/2 listener (h2 via ALPN, or cleartext h2c). Import your .proto or compiled .desc and every message — unary and server/client/bidi streaming — is decoded to JSON, matched by method, with the grpc-status on each row.

Reversee decoding gRPC: a traffic table of gRPC calls with grpc-status, and a detail pane showing the request and response protobuf messages as JSON.

✨ Made for AI agents

Reversee ships an MCP server, so Claude Code, Cursor, or any MCP client can inspect and control the proxy. Agents can debug your traffic for you — or run Reversee headless as part of an automation.

◆One-line setup. Register the server with a single command — no config files.
◆Read-only by default. Tools like list_traffic and get_traffic_entry are always safe; starting/stopping the proxy needs an explicit opt-in.
◆Local & private. The bridge talks to the app over a token-authenticated local socket — never a network port.
◆Headless mode. reversee --headless --allow-mcp-control runs with no UI for agents and CI.
◆Always current. The app owns the tool catalog, so new tools reach agents automatically on app updates.

Claude Code

claude mcp add reversee -- npx -y reversee-mcp

Cursor — ~/.cursor/mcp.json

{
  "mcpServers": {
    "reversee": { "command": "npx", "args": ["-y", "reversee-mcp"] }
  }
}
Reversee's Connect AI dialog showing the Claude Code command and Cursor JSON, with copy buttons.

Get going in under a minute

Install, point your client at it, and watch the traffic.

Install & launch Reversee

Download a build, or brew install --cask galusben/reversee/reversee.

Set the listen and destination

e.g. listen on http:8080, forward to https://api.example.com. Click Start.

Send a request

curl http://localhost:8080/api/users — it appears in the table; click it to inspect.

Intercept, breakpoint, or hand it to an agent

Rewrite a response in JS, hold a request to edit it, or connect Claude Code to do it for you.

Install

Signed and notarized on macOS. Updates itself from GitHub Releases.

macOS — Homebrew

brew tap galusben/reversee
brew install --cask reversee

macOS / Linux — one-liner

curl -fsSL https://raw.githubusercontent.com/\
galusben/reversee/main/install.sh | bash

All downloads (incl. Windows) ↗