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.

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.

Scripts

Rewrite requests or responses with a few lines of JavaScript: change headers, paths, bodies. Try a script on a captured request first, then apply it to the running proxy.

Mocks & routes

Answer any request with a response you write, or send part of the traffic to a different server. Record a whole session as mocks in one click. No code, and changes apply while the proxy runs.

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.

Compare two requests

Mark one request, compare it with another: status, headers and bodies side by side, JSON normalized, so you see why one call worked and the other failed.

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.

Mock any endpoint in seconds

Fake an endpoint that does not exist yet, force a 500, or slow a call down, without touching the backend. Pick a path, write the response, save: the running proxy answers the next request. Right-click any captured request and choose Mock This Response to start from the real thing. Routes work the same way, sending /api/v2 to a service on your machine while everything else goes to staging.

Reversee's Routes and mocks screen: a mock named Feature flags that answers GET /api/flags with a JSON body, a second mock returning 503 after a delay, and a note that it matches 2 of 4 captured requests.

Record a session, replay it offline

Click Record as mocks and every captured response becomes a mock: one per method and URL, with its status, headers and body, binary bodies included. Turn the backend off and the frontend keeps working; point a test at the proxy and it gets the same answers every time. Record everything, only what the filter lists, or a single request.

Reversee's Record as mocks dialog: the requests the filter lists become two new mocks, one per URL, previewed before saving.

Rewrite traffic with a few lines of code

When a fixed reply is not enough, write a script. Add a header to every API call, point /v1/ at /v2/, flip a field in a JSON response. Start from a one-click example, press Try it to see exactly what the script changes on a request you already captured, and save: the running proxy uses it on the next request, no restart.

Reversee's Scripts screen: a request script that adds an x-debug header to API calls, a list of what a script can change, one-click examples, and a Try it result showing the header that was added to a captured request.

Capture anything a program sends

Not sure which servers your app talks to? Switch to Capture anything and Reversee becomes a regular HTTP/HTTPS proxy. Set HTTPS_PROXY to its address and every request shows up, listed under the host it went to, with HTTPS decrypted. No URLs to change, and mocks, scripts, breakpoints and replay keep working.

Reversee in Capture anything mode: the settings bar shows the proxy address, and the traffic table lists requests to several hosts with a Host column.

Why did this call work and that one fail?

Right-click a request, Mark for Compare, then right-click another and choose Compare with. Reversee lists what differs in plain words, then shows the headers and bodies side by side. JSON is pretty-printed with sorted keys and compressed bodies are decoded, so only real differences stand out. Agents get the same diff from the compare_requests MCP tool.

Reversee's Compare requests screen: a summary listing status 200 to 401, a changed Authorization header and a header only in B, above a side-by-side diff of two JSON response bodies.

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.
◆Mock by asking. “Make /api/flags return this JSON” becomes one add_mock call, live on the running proxy. add_route redirects a path to another server, and record_mocks turns captured traffic into mocks.
◆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) ↗