About UserTapes
UserTapes MCP is a hosted server for teams and coding agents that need to inspect real website sessions. It turns replay activity into searchable transcripts and provides filters, aggregate statistics, and session alerts.
Key features
- 01List sites and recorded sessions
- 02Filter sessions by errors and activity
- 03Read session transcripts
- 04View aggregate session statistics
- 05Create and manage session alerts
Use cases
- 01Investigate errors seen during real visits
- 02Review user navigation and click activity
- 03Monitor sessions matching a defined condition
MCP support
Provides a stateless JSON-RPC endpoint over Streamable HTTP. MCP clients can query session data and manage alerts using a revocable, read-scoped token.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://usertapes.com/mcpclaude mcp add --transport http mcdca-usertapes https://usertapes.com/mcp{"mcpServers":{"mcdca-usertapes":{"type":"http","url":"https://usertapes.com/mcp"}}}Open in Cursor{"servers":{"mcdca-usertapes":{"type":"http","url":"https://usertapes.com/mcp"}}}Open in VS Code{"mcpServers":{"mcdca-usertapes":{"type":"http","url":"https://usertapes.com/mcp"}}}{"mcpServers":{"mcdca-usertapes":{"serverUrl":"https://usertapes.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
https://usertapes.com/mcpAuth requiredTools
Details
From the project READMEUserTapes 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.)
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.