LogRocket MCP Server

Query LogRocket session replays, metrics, and issues in natural language from AI coding assistants like Cursor, Claude, and Codex.

Analytics by LogRocket OAuth2 active

Connect (Remote Server) Docs

Overview

The LogRocket MCP server is a remote, provider-hosted server that brings LogRocket session replay, product analytics, and error tracking data into LLM-based clients such as Cursor, Claude Code, Claude Desktop, Codex, and VS Code. Once connected, an AI agent can pull live context about how users interact with your app, what errors are firing, and what sessions reveal about a bug, all via natural language queries against LogRocket's API.

The server exposes a small set of default tools (listing organizations, listing projects, and a natural language query tool powered by LogRocket's "Ask Galileo" assistant), and additional toolsets can be opted into via a query string parameter on the server URL. Available toolsets include sessions (find and analyze sessions), metrics (query analytics data), ask-galileo (natural language queries), and all. Access can be scoped to an organization or a specific project by appending path segments to the server URL.

Authentication is via OAuth (recommended), which automatically grants the MCP client access to the organizations and projects visible to the signed-in user. As an alternative, project-scoped API keys can be used via a Bearer Authorization header. LogRocket notes that the tools are under active development and subject to change.

Tools

Tool	Description
`list_organizations`	Lists LogRocket organizations the authenticated user can access.
`list_projects`	Lists projects within an accessible LogRocket organization.
`use_logrocket`	Runs a natural language query against LogRocket data using the Ask Galileo backend.
`sessions toolset`	Optional toolset for finding and analyzing user sessions. Enabled via ?toolsets=sessions.
`metrics toolset`	Optional toolset for querying LogRocket analytics and metrics. Enabled via ?toolsets=metrics.
`ask-galileo toolset`	Default natural language query toolset powered by LogRocket Ask Galileo.

Setup Guide

Prerequisites

A LogRocket account with access to one or more organizations/projects
An MCP-compatible client (Cursor, Claude Code, Claude Desktop, Codex, or VS Code)
For API key auth (optional): a project-scoped API key generated in Settings > API Keys in LogRocket

Server URL

https://mcp.logrocket.com/mcp

Optional scoping:

https://mcp.logrocket.com/mcp/<organization_id>
https://mcp.logrocket.com/mcp/<organization_id>/<project_id>

Optional toolsets:

https://mcp.logrocket.com/mcp?toolsets=sessions,metrics

Valid toolset values: sessions, metrics, ask-galileo, all.

Cursor

Add to your Cursor MCP config:

{
  "mcpServers": {
    "logrocket": {
      "url": "https://mcp.logrocket.com/mcp"
    }
  }
}

Claude Code

Run from a terminal:

claude mcp add --transport http logrocket https://mcp.logrocket.com/mcp

Claude Desktop

Go to Settings > Connectors > Add custom connector and enter:

Name: LogRocket
URL: https://mcp.logrocket.com/mcp

Codex

codex mcp add logrocket --url https://mcp.logrocket.com/mcp

Then authenticate via the Codex login command.

VS Code

Run MCP: Add Server, choose HTTP, paste https://mcp.logrocket.com/mcp, and authenticate. Or add to mcp.json:

{
  "servers": {
    "logrocket": {
      "type": "http",
      "url": "https://mcp.logrocket.com/mcp"
    }
  }
}

Authentication

OAuth (recommended): Sign in via the browser flow when the client first connects. Access is automatically scoped to the orgs/projects your LogRocket user can see.
API Key: Pass a project-scoped key as a Bearer token in the Authorization header field exposed by your MCP client.

Use Cases

Investigate a production bug by asking the agent to find recent sessions where a specific error fired and summarize the user actions leading up to it.
Pull product analytics on the fly: "What is my 7-day funnel conversion from signup to first action?" without leaving the IDE.
Triage issues during code review by asking the agent to fetch sessions affected by the error tied to the file you are editing.
Query a single user's or account's sessions to support customer-specific debugging or success investigations.
Limit an MCP integration to one project via path scoping so different repos can connect to different LogRocket projects safely.

Example Prompts

"List the LogRocket organizations and projects I can access."
"Find sessions in the last 24 hours where users hit a JavaScript error on the checkout page and summarize what they did."
"Show me the top 5 issues by user impact this week in the web-app project."
"Pull metrics on the signup funnel for the last 30 days and break down drop-off by step."
"Find recent sessions for user alice@example.com and tell me which features she used."

Pros

Officially hosted and maintained by LogRocket, no self-hosting or local install required.
Supports OAuth so access automatically matches the user's existing LogRocket permissions.
Flexible scoping: limit the MCP connection to an organization or single project via URL path.
Modular toolsets (sessions, metrics, ask-galileo) can be enabled per connection.

Limitations

Tools are documented as under active development and subject to change.
Limited public tool surface (three default tools); deeper functionality is gated behind opt-in toolsets and the Ask Galileo natural language layer.
Requires a LogRocket plan with API access; full capabilities depend on what your LogRocket subscription exposes.

Alternatives

Sentry MCP Server for error tracking and issue triage.
PostHog MCP for product analytics and session replay queries.
Datadog MCP integrations for broader application performance and log analysis.