MCP server docs

Connect

Get a token from Agent access if you already have an account, or sign up free — every plan, including the free one, gets unlimited MCP access, no card required.

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

Claude Code, one line:

Claude Desktop only accepts OAuth connectors in its built-in UI today, so bridge the token through mcp-remote instead:

{
  "mcpServers": {
    "usertapes": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://usertapes.com/mcp", "--header", "Authorization: Bearer YOUR_MCP_TOKEN"]
    }
  }
}

Tools

• list_sitesThe account's sites.
• list_tapesSessions for a site, newest first. Filters: has_errors, has_rage_clicks, url_contains, min_duration_seconds, created_after/created_before. Each result carries a one-line derived summary.
• read_transcriptOne session as a markdown transcript — every navigation, click, error, and stall, timestamped to match the human player.
• get_statsAggregate counts over N days: session totals, error/rage-click counts, duration stats, top entry URLs, countries.
• site_digestA one-call markdown briefing of a site's recent activity, built from persisted per-tape summaries — no LLM call, instant.
• list_alertsSaved standing watches on a site's sessions.
• create_alertCreate a watch — e.g. "notify when a session hits an error on /checkout" — with optional email and/or webhook delivery.
• delete_alertDelete a saved alert by id.

Auth & scope

The bearer token is a distinct, revocable, read-scoped credential from the Agent access page — separate from a site's tracking token, which is ingest-only and sits in public page source by design. Its only write surface is alerts: it cannot delete a recording, change a site, or touch billing. There is no anonymous or unauthenticated access — every request is scoped to the account whose token it carries.