UserTapes

io.github.mcdcaPublished by GitHub account mcdcav1.0.1Updated Oct 25, 2026

Query real user session replay data: tapes, transcripts, error/rage-click filters, alerts.

VerifiedStreamable HTTPWeb executableDeveloper ToolsData & Analytics

Overview

AI-generated overview

UserTapes is a hosted MCP server that lets an assistant query real user session replay data — tapes, transcripts, errors and alerts — from your sites.

What you can do
List the account's sites and their recorded sessions, newest first, filtered by errors, rage clicks, URL substring, duration and date range. Read a single session as a markdown transcript of clicks, navigation and errors. Get aggregate counts over a number of days, or a one-call briefing of the last N days. List, create and delete saved alerts that watch sessions for conditions such as an error on a checkout page.
When to use it
Useful when debugging a problem users hit on your site and you want the assistant to see what real people actually did, rather than exporting a video. Also handy for periodic digests of recent sessions and for setting standing watches on error or rage-click patterns.
Requirements
A remote endpoint at usertapes.com/mcp over Streamable HTTP; no package install or local process. A UserTapes account and a bearer token from the Agent access page, sent in the Authorization header.
Before you install
The Authorization bearer token is a credential; keep it private and revoke it if exposed. The token can create and delete alerts, which changes account state. Session data from your sites is sent to the assistant through the hosted service.

Installation

In SourceWeft

  1. Open UserTapes in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.mcdca%2Fusertapes-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "usertapes": {
      "type": "http",
      "url": "https://usertapes.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

UserTapes MCP Server

UserTapes is a session replay tool. This is its Model Context Protocol server: a hosted, stateless JSON-RPC endpoint that lets any MCP client — Claude Code, Claude Desktop, Cursor, or your own agent — query what real users did on your site.

This repo does not contain the server's application source (that lives in the main UserTapes codebase). It exists to document and register the public connection details: the endpoint, its tools, and how to authenticate.

Why

Your coding agent can read your repository, your git history, and your test output. None of that describes what a real person actually did when something broke. UserTapes derives a text transcript from every recorded session — clicks, navigation, errors, rage clicks — so an agent can query sessions the same way it queries anything else, instead of you exporting a video and pasting it into a prompt.

Connecting

The server is one HTTP endpoint speaking stateless JSON-RPC 2.0 over Streamable HTTP (protocol revision 2025-06-18). Get a token from your account's Agent access page, then add:

json
{  "mcpServers": {    "usertapes": {      "url": "https://usertapes.com/mcp",      "headers": { "Authorization": "Bearer YOUR_MCP_TOKEN" }    }  }}

No package install, no local process — the client talks to https://usertapes.com/mcp directly.

Tools

ToolWhat it does
list_sitesThe account's sites
list_tapesSessions for a site, newest first, filterable by errors, rage clicks, URL substring, duration, and date range
read_transcriptOne session as a markdown transcript
get_statsAggregate counts over N days
site_digestOne-call briefing of the last N days
list_alerts / create_alert / delete_alertSaved standing watches over sessions (e.g. "notify when a session hits an error on /checkout")

The MCP token is a distinct, revocable, read-scoped credential — separate from a site's ingest-only tracking token. Its only write surface is alerts; it cannot delete a recording, change a site, or touch billing.

Docs

License

MIT — see LICENSE. (This repo is documentation and a registry manifest; the UserTapes application itself is closed source.)

Source: README.md at commit 546400e

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts