MCP Server

Summary

An MCP (Model Context Protocol) server that enables Claude and other MCP clients to query the LogRocket API in natural language to access information about your LogRocket sessions, metrics, issues, and more. For example, allows you to:

Pull in context about your app's behavior to help with debugging and fixing errors
Get a better sense of how users interact with your app
Query a user or account's sessions for targeted investigation

See Ask Galileo for information about what the LogRocket MCP can help with.

Setup

The LogRocket MCP Server is quick & easy to setup! To begin you will need your App ID, which can be found under Settings > Project Settings, or in the URL for your LogRocket dashboard. For example, an App ID of foo/bar is composed of an org ID foo and a project ID bar. Using those values the URL for configuring the MCP Server will be:

https://mcp.logrocket.com/mcp/<your_org_id>/<your_project_id>

This URL should be used when configuring the LogRocket MCP connection.

Cursor

Press ⌘ + Shift + J to open Cursor Settings.
Select Tools & MCP.
Select New MCP Server.

{
  "mcpServers": {
    "logrocket": {
      "url": "https://mcp.logrocket.com/mcp/<your_org_id>/<your_project_id>"
    }
  }
}

Connect to the MCP Server in the settings screen to authenticate.

VS Code

Press ⌘ + P and search for MCP: Add Server.
Select HTTP (HTTP or Server-Sent Events.
Enter the URL from above (e.g. https://mcp.logrocket.com/mcp/<your_org_id>/<your_project_id>) and hit enter.
Enter the name LogRocket and hit enter.
Follow the prompts to authenticate.
Activate the server using MCP: List Servers and selecting LogRocket, and selecting Start Server.

Claude Code

Open your terminal to access the CLI.
claude mcp add --transport http logrocket https://mcp.logrocket.com/mcp/<your_org_id>/<your_project_id>.
Follow the prompts to authenticate.
You may need to manually authenticate if it doesn't happen automatically via /mcp.

Available Tools

`use_logrocket`

Run a natural language query against LogRocket. Chains tool calls internally to limit context usage. Offers the same functionality as Ask Galileo in the LogRocket dashboard.

Example:

"Use LogRocket to tell me how many users have gone through the refills flow today."

...

"On average, how long did it take them to complete the flow?"

...

"How can we improve the flow to reduce the number of users who abandon it?"

`query_logrocket_user`

Deprecated. Use use_logrocket instead.

Query LogRocket by user email to get information about their sessions.

Example:

"Can you check LogRocket for user [email protected] and tell me what errors they encountered?"

`query_logrocket_sessions`

Deprecated. Use use_logrocket instead.

Query LogRocket for specific sessions by URL. Use this when you have a LogRocket session URL.

Session URL format: https://app.logrocket.com/<your_org_id>/<your_project_id>/s/<recordingID>/<sessionID>

Example:

"What errors occurred in this session: https://app.logrocket.com/logrocket/example/s/abc123/456"