UserProof

Session replay MCP server: run UserProof from Claude Code, Codex or Cursor

Updated . By Ryan Doyle, founder of UserProof, a session replay tool for coding agents. For founders shipping with Claude Code, Codex or Cursor.

UserProof is a session replay MCP server with 14 tools, built for founders who build with a coding agent. Install the plugin in Claude Code, or add one stdio server in Codex, Cursor or any MCP agent. The agent sets up recording, then returns the top fix from real visitor sessions. Free covers 3 sites and 5,000 visits a month.

We counted the tools in the server source on November 8, 2026: 14 are registered. A live tools/list run on November 7, 2026 also listed 14 (output on the install page). PostHog's tools reference, read the same day, lists 9 for session replays alone, inside a server that covers every PostHog product. UserProof's 14 do one job: find the fix, then check it worked.

Jump to: which agent, which install · the 14 tools · set it up · limits · where others win · price · FAQ

Which agent, which install?

Every agent below runs the same server. Claude Code gets it as a plugin; the others start it as a local stdio MCP server with npx.

AgentHow it connectsCommand or fileSteps
Claude CodePlugin (includes the MCP server and the setup and review commands)claude plugin marketplace add GetUserProof/userproof && claude plugin install userproof@userproofSet up in Claude Code
Codex (CLI or IDE extension)Local stdio MCP server; raise the start timeout to 60 secondscodex mcp add userproof -- npx -y github:GetUserProof/userproofInstall in Codex or Cursor
CursorLocal stdio MCP serverAn entry named userproof in ~/.cursor/mcp.jsonInstall in Codex or Cursor
ChatGPT desktop appLocal stdio MCP server, shared with CodexSettings, MCP servers, same npx commandConnect ChatGPT
VS Code, Windsurf, Claude Desktop or another MCP agentLocal stdio MCP servernpx -y github:GetUserProof/userproof, written in each agent's own config formatMCP config generator
ChatGPT in a web browserNot supported: no remote serverNoneWhy not

What can the agent do with the 14 tools?

It can read the top fix, set up and prove recording, and check a shipped fix. We counted the tools in the server source on November 8, 2026 (14 registered; server version 3.10.0, as the server reports itself) and read what each does there. Every tool answers in plain text, so any agent can use it.

JobToolWhat it returns
Read findingsget_top_fixThe single highest-impact fix on the site, the sessions that prove it, and dollar math when a conversion event is set. It adds a notice when the plan's visit limit is near.
fleetAll your sites in one read: the top fix or biggest leak for each, plus patterns that repeat across sites.
Pick the sitelist_sites, select_siteThe sites on the account with their ids, and the choice of which one this project uses. The agent saves it to .userproof in your repo.
Set up recordingwait_for_first_eventWaits up to 90 seconds for the first event from your site and says what arrived and from where. If nothing arrives, it returns the likely cause.
check_coverageWhich pages in your sitemap are missing the script tag.
set_goal, set_industryThe goal (a click or a page visit, with an optional dollar value) that findings are ranked by, and an industry tag for anonymous peer comparisons.
Before trafficscan_siteA read-only scan of the live site that returns the one worst defect it can reproduce 3 of 3 times. Takes 1 to 3 minutes; 10 a day per site.
Close the loopmark_fix_applied, check_fixRecords that a fix is live, then compares the finding's signal, the share of sessions that go on to a next step, and conversion before and after. It says "inconclusive" when traffic is thin.
Accountget_usage, get_activation, upgradeVisits used against the plan limit, the minutes from signup to each setup milestone, and a checkout link for Pro or Scale.

The Claude Code plugin adds commands on top of the tools: /userproof:setup and /userproof:review. The review command gets the top fix, finds the code to change and, after you ship, runs the check. For what counts as a dead or rage click, see how UserProof finds them.

How do I set it up?

You do four things; the help pages hold the exact steps so this page does not repeat them.

  1. Connect the server to your agent. Use the row for your agent in the table above. Done looks like the agent listing userproof as an enabled MCP server (codex mcp list or claude plugin list), then a restart so the tools load.
  2. Ask the agent to set up UserProof. In Claude Code that is /userproof:setup; elsewhere you tell it to read https://getuserproof.com/setup.md and follow it. You open one sign-in link in your browser. Done looks like the agent reporting status received: the script tag records.
  3. Let visitors arrive, then ask "what should I work on?" Done looks like one problem with the sessions that prove it. The count and thresholds are in the dead and rage click rules.
  4. Ship the fix and mark it. Done looks like the fix recorded as applied; the check then compares before and after.

The key is written to ~/.config/userproof/key by the sign-in step, so nothing secret goes into a config file. The plugin reads only .userproof in your repo and that key, and does not upload your source code.

What can the agent not do?

Where do PostHog's and Clarity's MCP servers still win?

They win when you already run that product and want its data, which ours does not hold. Both facts below were read on November 8, 2026.

The difference is in what comes back. Those servers return your data for you to question. UserProof's returns one ranked fix and then checks it. If you want to explore, pick theirs; if you want to be told what to change, pick ours.

What does it cost?

PlanPriceRecorded visits a monthSitesRecordings kept
Free$05,00037 days
Pro$29 a month50,000Unlimited90 days
Scale$99 a month250,000Unlimited90 days

Read from our pricing page on November 8, 2026. Every tool is on every plan. Past your plan's visits, UserProof keeps recording 1 in 4 visitors; nothing is cut off. To write the config for a second agent, use the MCP config generator, which runs in your browser.

To see this server beside the others a founder might add, read MCP servers for coding agents, ranked.

Sources, read November 8, 2026

FAQ

What is a session replay MCP server?

It is a program your coding agent starts that answers questions about recorded visitor sessions. UserProof's has 14 tools. The main one, get_top_fix, returns the highest-impact problem with the sessions that prove it. PostHog and Microsoft Clarity also publish MCP servers that read their own replay data.

Which coding agents can run the UserProof MCP server?

Claude Code through its plugin, and Codex, Cursor, the ChatGPT desktop app, VS Code, Windsurf or Claude Desktop through a local stdio server started with npx. It needs Node 18 or newer. ChatGPT in a web browser cannot use it, because there is no remote server.

Is an MCP session the same as a session replay session?

No. An MCP session is the connection between an agent and a server. A replay session is one visitor's visit to your site. UserProof's server runs over stdio on your machine, so there is no remote connection to keep alive. The sessions it reads are your visitors' recorded visits.

Does the agent edit my code or watch recordings by itself?

No tool edits code or plays a video. The server returns text: the finding, the sessions behind it and the numbers. Your agent decides what to change in your repo, and in Claude Code the review command finds the code for you. Nothing is marked fixed until you say the change is live.

Does running UserProof from an agent cost extra?

No. The server is free to run, and analyses and fix checks are unlimited on every plan. Plans are priced on recorded visits: Free is $0 for 3 sites and 5,000 visits a month, Pro is $29 a month for 50,000, Scale is $99 a month for 250,000.