Give your agents eyes

Session replay for
humans & machines

UserTapes turns every session into video for you and markdown for your agents. Ask “Did any users have a problem today?” — get an answer, timestamped, with the tape to prove it.

Works with Claude Cursor Gemini ChatGPT + More
🔒 usertapes.com/sites/acme
REC acme.app/checkout ⎘ Share ⛶ Fullscreen
Tapes Event stream Details
Why session replay

Stop guessing what
users actually do.

Analytics tells you what happened in aggregate. It won't tell you why someone hesitated, which feature nobody finds, or whether a bug report is one bad session or a pattern everyone's hitting. The session has that answer — everything below starts from watching real behaviour, not guessing at it.

Behaviour

See where people actually go, hesitate, and give up — not where you assumed they would.

Conversion

Watch the exact moment a signup, checkout, or trial falls apart — not just the drop-off rate.

Bugs

Reproduce nothing. The tape already has the repro steps, down to the click.

Trust

Settle “the user says…” arguments with a recording, not a debate.

Who it's for

Built for whoever's
closest to the users.

Different teams ask the tape different questions. The record, replay, and MCP loop is the same either way — what changes is who's asking and what they need to see.

Solo & indie

Understand your users without a research team.

Watch a handful of real sessions and you'll know more about how people actually use your product than a week of dashboards would tell you.

Best fit: Indie Deck →
Product & growth

Stop debating what users probably do.

Pull the sessions that prove — or kill — your next roadmap bet, and drop a timestamped link in Slack instead of a screen recording.

Best fit: Studio Deck →
Agencies & enterprise

One place, every client site.

Cookieless by default, seats for the whole team, and enough volume that nobody's rationing sessions across accounts.

Best fit: Broadcast Deck →
Modules

One tape, six ways to use it.

Every session, recorded once and handed to whoever's asking — video for you, plain text for your agents — as proof, not a summary. No charts pretending to be insight.

[ 01 ]

Record

See it happen, don't hear about it. Every session captured frame-by-frame — cookieless by default, inputs masked at the source, under 15 KB on the wire.

Learn more →
[ 02 ]

Serve · MCP

Your agent doesn't have to ask you what happened. A native MCP server exposes tapes as tools — Claude, Cursor, or your own agents query sessions like a database.

Learn more →
[ 03 ]

Read

Skip the video when you don't need it. Every session comes with a transcript — navigation, clicks and stalls narrated as plain text your agents can parse.

Learn more →
[ 04 ]

Replay

When you do need to see it, see all of it. Pixel-accurate playback in a hardware-grade deck — scrub, skip, and step through exactly what the user saw.

Learn more →
[ 05 ]

Index

Find the moment that mattered without watching the whole tape. Rage clicks, dead clicks, errors and drop-offs marked on the timeline as machine-readable events — not vibes.

Learn more →
[ 06 ]

Retain

Keep the evidence, not the storage bill. Retention windows you set per site — tapes expire on schedule, storage stays lean, and your bill stays flat.

Learn more →
Answer without watching

Chat with
your tape.

Every tape comes with an agent that has already read it. Ask why the visitor left, what broke, whether they ever paid — and get an answer grounded in the recording, never a guess. Timestamps in the answer are buttons: press one and the player jumps to that exact moment.

  • GroundedAnswers cite the tape's own transcript — if it isn't recorded, it isn't claimed
  • Seek“It broke at 0:40” is a button — click it, watch it break
  • Site-wideThe site console answers across every session — “who failed checkout this week?” — with links into each tape
  • PrivateInputs are masked at record time; the agent reads what the visitor did, not what they typed
More on Ask your tape →
Agent · Tape 3E71
Claude Code · UserTapes MCP
$ claude "users say coupons are broken — find it and fix it" ────────────────────────────────────── ▸ usertapes list_tapes(has_errors: true) ← 14 tapes · rage clicks on "Apply coupon" ▸ usertapes read_transcript(3e7128f8) ← ## Transcript - 0:19 click button "Apply coupon" - 0:20 ⚠ POST /api/coupon · 422 - 0:23 ⚠ rage click ×4 · same button ▸ diagnosis: checkout.js swallows 422s — no error shown, button stays live ▸ editing checkout.js +14 −3 ✓ fixed — from the tape, not a guess
Fix without reproducing

Hours of tape,
read in seconds.

Connect Claude Code, Cursor, or your own tooling over MCP and the agent does the watching: every session scanned, the ones that matter surfaced — where users struggle, what broke, who almost converted — each insight linked to the exact tape. And when the cause turns out to be a bug, the same agent can go fix it.

  • ProtocolModel Context Protocol — works with Claude Code, Cursor, and any MCP client
  • Toolslist_tapes · read_transcript · create_alert — filters for rage clicks, errors, URLs, duration
  • SetupOne URL + one token in your agent's MCP config. No SDK, no glue code.
  • Standing ordersAgents set their own alerts — matching sessions webhook straight back to them
Trust without asking

Seeing is still
believing.

Agents read tapes; you can still watch them. Every session plays back frame-by-frame — because the fastest review of an agent's diagnosis is watching the thirty seconds where it happened, and the fastest way to trust a fix is seeing what it fixes.

  • SignalsRage clicks, dead clicks, errors, reload loops, abandoned forms — marked in red on the scrubber
  • ReadoutEvery navigation, click and stall as a timestamped stream — click a row, the tape seeks there
  • TransportSkip idle · 1× 2× 4× — a 9-minute session in ninety seconds
  • ShareView-only links that open at the exact second you're pointing at
More on Replay & transcripts →
How it works

Live in three steps.

No meetings, no sales calls, no infrastructure to provision — installing takes less time than reading this page.

[ 01 ]

Install the snippet

One script tag, under 15 KB. Cookieless by default — nothing to configure, no consent banner to add.

[ 02 ]

Watch & chat immediately

Every session plays back frame-by-frame the moment it lands. Ask it what happened and get an answer grounded in the recording.

[ 03 ]

Connect MCP, ask from your agent

One URL and one token in your agent's MCP config. Claude Code, Cursor, or your own tooling can query every session like a database.

Pricing

Every tier, cookieless.

Pricing scales with volume, nothing else. Every deck ships the same cookieless tracker, inputs masked at the source, and full MCP access — pick the one that matches how much you record, and upgrade when the counter says so.

Demo Tape
$0 /mo

Point it at a real site. No card, no expiry date.

  • 1,000 sessions / mo
  • 7-day retention
  • 1 site
  • Chat — 50 questions / mo
  • MCP access — unlimited
Start free
Recommended Indie Deck
$29 /mo

$24/mo billed annually

For solo developers running active production apps.

  • 15,000 sessions / mo
  • 30-day retention
  • 3 sites · 1 seat
  • Email support
  • Unlimited MCP access
Start recording
Studio Deck
$59 /mo

$49/mo billed annually

Engineered for product teams, integrations, and AI pipelines.

  • 50,000 sessions / mo
  • 30-day retention
  • 5 sites · 5 seats
  • Slack, Linear & Jira integrations
  • Unlimited MCP access
Start recording
Broadcast Deck
$149 /mo+

High-fidelity pipeline for agencies & high-volume platforms.

  • Custom volume — 100k+ sessions / mo
  • 90-day retention
  • Unlimited sites & seats
  • Dedicated Slack channel
  • Unlimited MCP access
Talk to us
Compare every feature across plans
Demo Tape Indie Deck Studio Deck Broadcast Deck
Sessions1,000/mo15,000/mo50,000/mo100k+/mo
Retention7 days30 days30 days90 days
Sites · seats1 · 13 · 15 · 5Unlimited
Chat with your tapes*50 questions/mo
Event alerts
MCP access
Shareable linksWhitelabelWhitelabel
Rate limitsStandardStandardPriorityZero (dedicated gateway)
IntegrationsSlack, Linear, JiraSlack, Linear, Jira
SupportCommunityEmailPriority emailDedicated Slack channel

* Fair use on chat: usage well outside what's typical for your plan may get a friendly note from us — never a silent cutoff.

FAQ

Before you connect a site.

The short version of things people usually ask.

Do I need a cookie banner?

No. UserTapes is cookieless by default — no cookies, no fingerprinting, nothing that needs consent. The tracker just records the session and reports back.

Which agents actually work with this?

Any MCP client. We've verified Claude Code, Claude, Cursor, Gemini, and ChatGPT — point your agent's MCP config at one URL and one token and it can query sessions immediately. No SDK, no glue code.

Can my agent (or I) see what visitors typed?

No. Every input is masked at the source, before it ever leaves the visitor's browser. What you and your agent see is that a field was filled in — never the value, not even for a second.

What's the actual difference between the free plan and a paid deck?

Session volume, retention window, and site/seat count scale with the plan you're on. MCP access itself is unlimited on every tier — including the free Demo Tape.

What happens if I go over my plan's session limit?

You'll hear from us, not get cut off mid-session. Usage well outside what's typical for your plan gets a friendly nudge to upgrade — never a silent wall.

How is this different from Hotjar or FullStory?

Those are built for a human to dig through a dashboard. UserTapes is built to be asked a question — by you or by your agent — and every answer cites the exact tape and timestamp it came from, not a chart.

Do I need to install an SDK?

No. One tracking snippet on your site, under 15 KB on the wire, and one line in your agent's MCP config. That's the entire integration.

What happens to a tape once its retention window ends?

It expires automatically on the schedule you set per site — no manual cleanup, storage stays lean, and your bill stays flat.

Start now

Press and ask.

One snippet on your site, one line in your agent's MCP config. Your next question about users takes seconds — not an afternoon of tape.