OpenReplay MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsB | Get list of all projects in the organization |
| get_user_sessionsB | Get sessions for a specific user ID (API key authentication supported) |
| search_sessionsA | [Requires userId with API key auth] Search and filter sessions. Full search requires JWT authentication. |
| get_session_detailsC | Get detailed information about a specific session including all events, errors, network requests, console logs, custom events, and performance metrics |
| get_session_eventsC | Get all events from a session with optional filtering by event type |
| aggregate_sessionsB | Aggregate session data with various metrics and groupings |
| get_user_journeyC | Get the complete journey of a user across multiple sessions |
| get_errors_issuesC | Get errors and issues with their impact and affected sessions |
| get_funnel_analysisC | Analyze user funnels and conversion paths |
| get_performance_metricsC | Get performance metrics like page load times, largest contentful paint, time to interactive, etc. |
| execute_custom_queryC | Execute a custom query on the session data (supports SQL-like syntax for ClickHouse) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools have distinct purposes, such as aggregate_sessions for metrics, get_session_details for comprehensive data, and get_funnel_analysis for user paths. However, get_session_events and get_session_details could be confused as both retrieve session data, though their scopes differ (events only vs. all details).
All tool names follow a consistent verb_noun pattern using snake_case, such as aggregate_sessions, get_session_details, and list_projects. This uniformity makes the tool set predictable and easy to navigate for an agent.
With 11 tools, the count is well-suited for a session analytics domain, covering key operations like querying, analyzing, and managing sessions and projects. Each tool appears purposeful without being overwhelming or insufficient.
The tool set provides strong coverage for session analytics, including data retrieval, aggregation, error analysis, and user journey tracking. A minor gap exists in management operations, such as creating or deleting sessions or projects, but core analytical workflows are well-supported.