What is a #session-replay MCP server?
An MCP server tagged #session-replay implements the Model Context Protocol so AI assistants like Claude, Cursor, and VS Code can access session-replay-related tools, data, or APIs.
Every MCP server and client below is tagged #session-replay — install one to give Claude, Cursor, VS Code, or any other MCP-compatible client access to session-replay tools.
rollbar
Model Context Protocol server for Rollbar
Fullstory
Product analytics with receipts. Claude builds segments, computes metrics, and analyzes conversion from your Fullstory behavioral data, then pulls the real sessions behind every number. Requires a Fullstory account on an
Cubenest
Two OSS products on one rrweb substrate: tracelane (self-contained HTML test-failure replays for WDIO/Playwright/Cypress) + peek (local-first browser-session forensics + repro for AI coding agents, over MCP). No SaaS, no telemetry, local-first.
fullstorydev
The Fullstory MCP server connects your AI assistant directly to your Fullstory product data. Using the Model Context Protocol, it lets any MCP compatible AI client (Cursor, Claude Desktop, Claude Code, and others) query your Fullstory data, analyze user behavior, and surface insi
Common questions about MCP servers and clients tagged #session-replay
An MCP server tagged #session-replay implements the Model Context Protocol so AI assistants like Claude, Cursor, and VS Code can access session-replay-related tools, data, or APIs.
mcp.so currently lists 4 MCP servers and clients tagged #session-replay.
Open any server below and copy its install snippet into Claude Desktop, Cursor, VS Code, or another MCP client's configuration — remote servers need no separate download.