LogRocket MCP Server
An MCP server for integrating LogRocket data with your LLM applications
Summary
An MCP (Model Context Protocol) server that allows Cursor, Claude Code, Codex, 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 server can help with.
Example Prompts
Here are some examples of how you can use the LogRocket MCP server in your AI-assisted workflow:
- Fix user-reported issues: "User X reported a problem with checkout. Can you use LogRocket to watch their sessions, figure out the root cause, and fix it?"
- Understand feature usage: "I'm about to work on the search feature — can you use LogRocket to help me understand how it's currently being used?"
- Triage new issues: "Can you look at LogRocket for new issues from the past week, try to figure out their root causes, and then suggest which ones I can fix?"
- Check for regressions: "Look at all commits from last week, and check LogRocket data to ensure they didn't introduce any regressions."
- Prioritize your work: "Use LogRocket to watch sessions and look at issues to figure out what is highest priority that I work on next."
Suggested Automations
Because the MCP server can be called programmatically by AI agents, you can also set up powerful automations that continuously leverage LogRocket data:
- Research churning customers and low NPS scores: Automatically pull LogRocket sessions for users who are churning or leaving low NPS scores to understand what went wrong in their experience.
- Research new support tickets: Connect to your help desk to automatically research incoming support tickets using LogRocket session data. LogRocket offers out-of-the-box integrations with Zendesk and Intercom to attach session replays directly to tickets.
- Summarize user behavior for sales and customer success: Automatically generate summaries of how key accounts are using your product, giving your sales and customer success teams actionable insights.
- Connect LogRocket with your backend data: Build a skill that allows your agent to correlate LogRocket frontend data with backend observability tools (e.g., Datadog MCP) for end-to-end debugging.
- Run daily or weekly reports: Schedule an agent to look for new issues and UX frustration signals on a recurring basis, so your team is always aware of emerging problems.
Setup
The LogRocket MCP server is available at https://mcp.logrocket.com/mcp. The setup instructions below use this URL. It allows your MCP client to access the same LogRocket organizations and projects you can access in your browser.
You can also choose to restrict your MCP client's access to a specific LogRocket organization or LogRocket project by adding to the MCP server URL's path:
- To scope to an organization, use
https://mcp.logrocket.com/mcp/<your_organization_id> - To scope to a project, use
https://mcp.logrocket.com/mcp/<your_organization_id>/<your_project_id>
You can find organization and project IDs in most LogRocket URLs (e.g., https://app.logrocket.com/<your_organization_id>/<your_project_id>/s/...). You can also find them in the LogRocket dashboard under Settings > Project Settings. The App ID listed there has the form <your_org_id>/<your_project_id>.
Cursor
To install manually:
- Press
⌘+Shift+Jto open Cursor Settings. - Select Tools & MCP.
- Select New MCP Server.
-
{ "mcpServers": { "logrocket": { "url": "https://mcp.logrocket.com/mcp" } } } - Connect to the MCP server in the settings screen to authenticate.
Claude
Claude Code
- Open your terminal to access the CLI.
- Run
claude mcp add --transport http logrocket https://mcp.logrocket.com/mcp - Follow the prompts to authenticate.
- If authentication doesn't happen automatically, trigger it manually with
/mcp.
- If authentication doesn't happen automatically, trigger it manually with
Claude Desktop
- Navigate to Settings -> Connectors.
- Select Add custom connector.
- Enter a name (e.g., LogRocket) and LogRocket's remote MCP server URL,
https://mcp.logrocket.com/mcp. - Click Add.
- Click Connect next to newly-added LogRocket connector in the Connectors list to authenticate.
Codex
- Open your terminal to access the CLI.
- Run
codex mcp add logrocket --url https://mcp.logrocket.com/mcp - Run
codex mcp login logrocketand follow the prompts to authenticate.
VS Code
To install manually:
- Press
⌘+Pand search for MCP: Add Server. - Select HTTP (HTTP or Server-Sent Events).
- Enter the URL from above (e.g.,
https://mcp.logrocket.com/mcp) and hit enter. - Enter the name LogRocket and hit enter.
- Follow the prompts to authenticate.
- Activate the server using MCP: List Servers, selecting LogRocket, then selecting Start Server.
Updated 6 days ago
