UserTapes
Query real user session replay data: tapes, transcripts, error/rage-click filters, alerts.
Open source Repository Open in the app JSON README (API)
About
Query real user session replay data: tapes, transcripts, error/rage-click filters, alerts.
Details
- Kind
- MCP servers
- Topic
- Cloud & DevOps
- Publisher
- mcdca
- Origin
- official
- Category
- ferramentas
- Transport
- http
- Version
- 1.0.1
- Last push
- 2026-08-03T14:40:54Z
- Repository state
- ativo
- License
- MIT
- Added
- 2026-08-29 04:00:29
- Updated
- 2026-08-29 04:00:29
- Origin id
io.github.mcdca/usertapes-mcp
README
# UserTapes MCP Server
[UserTapes](https://usertapes.com) is a session replay tool. This is its
[Model Context Protocol](https://modelcontextprotocol.io) 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
| 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](https://usertapes.com/docs/mcp) — endpoint, auth, connection config, full tool reference
- [MCP agent access](https://usertapes.com/features/mcp-server) — feature overview
- [Session replay over MCP](https://usertapes.com/blog/session-replay-mcp-server) — full protocol details and tool schema
## License
MIT — see [LICENSE](LICENSE). (This repo is documentation and a registry
manifest; the UserTapes application itself is closed source.)