UserTapes
Query real user session replay data: tapes, transcripts, error/rage-click filters, alerts.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http usertapes 'https://usertapes.com/mcp' --header 'Authorization: <Bearer token from your UserTapes Agent access page (Settings > Agent access).>'{
"mcpServers": {
"usertapes": {
"type": "http",
"url": "https://usertapes.com/mcp",
"headers": {
"Authorization": "<Bearer token from your UserTapes Agent access page (Settings > Agent access).>"
}
}
}
}Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
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:
{
"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
| Tool | What it does |
|---|---|
list_sites | The account's sites |
list_tapes | Sessions for a site, newest first, filterable by errors, rage clicks, URL substring, duration, and date range |
read_transcript | One session as a markdown transcript |
get_stats | Aggregate counts over N days |
site_digest | One-call briefing of the last N days |
list_alerts / create_alert / delete_alert | Saved 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
- MCP server docs — endpoint, auth, connection config, full tool reference
- MCP agent access — feature overview
- Session replay over MCP — full protocol details and tool schema
License
MIT — see LICENSE. (This repo is documentation and a registry manifest; the UserTapes application itself is closed source.)
Frequently asked questions
What is UserTapes?
Query real user session replay data: tapes, transcripts, error/rage-click filters, alerts.
How do I install UserTapes?
It runs as a remote server. In Claude Code: claude mcp add --transport http usertapes 'https://usertapes.com/mcp' --header 'Authorization: <Bearer token from your UserTapes Agent access page (Settings > Agent access).>'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does UserTapes need an API key?
Yes. It expects Authorization, which you set in its configuration.
Is UserTapes open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains UserTapes?
It is published by mcdca. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.