LogRocket MCP

1. Install the SDK

   Node.js

   npm install @scalekit-sdk/node

   Python

   pip install scalekit

   Full SDK reference: Node.js | Python

2. Set your credentials

   Add your Scalekit credentials to your .env file. Find values in app.scalekit.com > Developers > API Credentials.

   .env

   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>

3. Authorize and make your first call

   Node.js

   quickstart.ts

   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   
   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENV_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions
   
   const connector = 'logrocketmcp'
   const identifier = 'user_123'
   
   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize LogRocket MCP:', link)
   process.stdout.write('Press Enter after authorizing...')
   await new Promise(r => process.stdin.once('data', r))
   
   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'logrocketmcp_list_organizations',
     toolInput: {},
   })
   console.log(result)

   Python

   quickstart.py

   import os
   from scalekit.client import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()
   
   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENV_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions
   
   connection_name = "logrocketmcp"
   identifier = "user_123"
   
   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize LogRocket MCP:", link_response.link)
   input("Press Enter after authorizing...")
   
   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="logrocketmcp_list_organizations",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)

What you can do

Connect this agent connector to let your agent:

• Sessions watch, find — Use this to analyze one or more LogRocket sessions, each identified by its recording ID and session ID
• Get network entries — Use this to retrieve raw network request and response pairs recorded during a single LogRocket session, identified by its recording ID and session ID, as a HAR 1.2 document
• Issues find — Use this to list a LogRocket project’s issues
• Metric build — Use this to query LogRocket analytics data
• Logrocket use — Process a natural language query against LogRocket data — sessions, metrics, and issues
• List projects, organizations — List all projects within a LogRocket organization

Tool list

Use the exact tool names from the Tool list below when you call execute_tool. If you’re not sure which name to use, list the tools available for the current user first.

logrocketmcp_build_metric#Use this to query LogRocket analytics data. This tool translates your natural language query into a LogRocket metric (e.g., timeseries, table, conversion funnel) that is then used to find relevant data. It's best used for performing aggregate analysis (e.g., session totals over time, browser or country breakdowns, conversion rates between steps). Returns an object with a `metricDefinition` field indicating the LogRocket metric that was used to find the data and a `metricQueryResult` field containing the corresponding analytics data.5 params▾

Use this to query LogRocket analytics data. This tool translates your natural language query into a LogRocket metric (e.g., timeseries, table, conversion funnel) that is then used to find relevant data. It's best used for performing aggregate analysis (e.g., session totals over time, browser or country breakdowns, conversion rates between steps). Returns an object with a `metricDefinition` field indicating the LogRocket metric that was used to find the data and a `metricQueryResult` field containing the corresponding analytics data.

NameTypeRequiredDescription

organizationIDstringrequiredThe organization ID to run the query against. If not provided by the user, discover options using the list_organizations tool.

projectIDstringrequiredThe project ID to run the query against. If not provided by the user, discover options using the list_projects tool.

querystringrequiredNatural language query describing the analytics data you want to retrieve.

limitintegeroptionalMaximum number of rows/buckets returned in metricQueryResult for top-N or table-style metrics (e.g., top countries, top pages, top users). Defaults to 20. This does not control sessionDefinitions and may be ignored for metric types that do not return ranked row buckets.

timezonestringoptionalOptional IANA timezone (e.g., 'America/New_York'). Time buckets align to this timezone's calendar (e.g., daily buckets break at its midnight). When omitted, they align to UTC.

logrocketmcp_find_issues#Use this to list a LogRocket project's issues. This includes error signals detected in session recordings, specifically JavaScript exceptions, network errors, rage clicks, dead clicks, frustrating network requests, error states, and mobile crash reports. Issues can be filtered by severity, triage status, issue type, and time range, and optionally refined with a natural language query. Returns an object with an `issues` field listing matching issues, each with its issue type, platform, event count, first/last seen dates, `triageStatus`, a `url` linking to the issue's detail page in the LogRocket dashboard, and an AI-generated `issueDescription` when one exists.9 params▾

Use this to list a LogRocket project's issues. This includes error signals detected in session recordings, specifically JavaScript exceptions, network errors, rage clicks, dead clicks, frustrating network requests, error states, and mobile crash reports. Issues can be filtered by severity, triage status, issue type, and time range, and optionally refined with a natural language query. Returns an object with an `issues` field listing matching issues, each with its issue type, platform, event count, first/last seen dates, `triageStatus`, a `url` linking to the issue's detail page in the LogRocket dashboard, and an AI-generated `issueDescription` when one exists.

NameTypeRequiredDescription

organizationIDstringrequiredThe organization ID to run the query against. If not provided by the user, discover options using the list_organizations tool.

projectIDstringrequiredThe project ID to run the query against. If not provided by the user, discover options using the list_projects tool.

endDatestringoptionalOptional ISO 8601 datetime for the end of the time range to search. Defaults to now.

issueTypesarrayoptionalOptional list of issue types to include. "exception" covers JavaScript exceptions and mobile errors, "networkError" failed network requests, "mobileCrash" mobile app crash reports, "rageClick" repeated frustrated clicks, "deadClick" clicks with no visible effect, "frustratingNetworkRequest" impatient user actions during slow requests, and "errorState" error pages and modals users encounter. Defaults to all issue types.

limitintegeroptionalMaximum number of issues to fetch, applied before any natural language relevance filtering. Defaults to 30.

querystringoptionalOptional natural language query used to refine results (e.g., "checkout errors affecting Chrome users"). When provided, additional filters are parsed from the query and results are filtered to those relevant to it. Omit to list issues using only the structured parameters.

severitystringoptionalOptional severity filter. "severe" returns only issues where LogRocket detected significant user impact and generated an issue description; "notSevere" returns only issues without one; "any" returns both. Defaults to "severe".

startDatestringoptionalOptional ISO 8601 datetime for the start of the time range to search. Defaults to a lookback of one week. Issues data is only retained for 30 days: start dates older than that are clamped to 30 days ago, and time ranges ending more than 30 days ago return no issues.

triageStatusesarrayoptionalOptional list of triage statuses to include. Issues start as "untriaged" and can be triaged by users to "highImpact", "lowImpact", or "ignored". Defaults to ["untriaged"], matching the default dashboard issues view.

logrocketmcp_find_sessions#Use this to find LogRocket sessions matching a natural language query. This tool translates your natural language query into LogRocket filters that are then used to find relevant sessions. It's best used for filtering sessions based on user ID or email, custom user traits, visited page or URL, custom events, text inputs, clicked on text or CSS selector, network errors, IP address, user location (e.g., country), and/or other basic metadata, in addition to over a specific date range (e.g., last week). Returns an object with a list of relevant sessions in the `sessionDefinitions` field, each with recording ID, session ID, session URL, date of recording as a Unix timestamp in milliseconds, and other basic metadata. The returned object will also include a `metricDefinition` field indicating which LogRocket filters were used to find the sessions.4 params▾

Use this to find LogRocket sessions matching a natural language query. This tool translates your natural language query into LogRocket filters that are then used to find relevant sessions. It's best used for filtering sessions based on user ID or email, custom user traits, visited page or URL, custom events, text inputs, clicked on text or CSS selector, network errors, IP address, user location (e.g., country), and/or other basic metadata, in addition to over a specific date range (e.g., last week). Returns an object with a list of relevant sessions in the `sessionDefinitions` field, each with recording ID, session ID, session URL, date of recording as a Unix timestamp in milliseconds, and other basic metadata. The returned object will also include a `metricDefinition` field indicating which LogRocket filters were used to find the sessions.

NameTypeRequiredDescription

organizationIDstringrequiredThe organization ID to run the query against. If not provided by the user, discover options using the list_organizations tool.

projectIDstringrequiredThe project ID to run the query against. If not provided by the user, discover options using the list_projects tool.

querystringrequiredNatural language query describing the sessions you want to find.

limitintegeroptionalMaximum number of sessions to return. Defaults to 10.

logrocketmcp_get_network_entries#Use this to retrieve raw network request and response pairs recorded during a single LogRocket session, identified by its recording ID and session ID, as a HAR 1.2 document. Prefer this tool over watch_sessions when you only need network data. The response is an object with `total`, `offset`, `limit`, and `har`; entries are sorted by request start time and paginated, so if `offset + limit < total`, call the tool again with a higher offset to fetch the next page.12 params▾

Use this to retrieve raw network request and response pairs recorded during a single LogRocket session, identified by its recording ID and session ID, as a HAR 1.2 document. Prefer this tool over watch_sessions when you only need network data. The response is an object with `total`, `offset`, `limit`, and `har`; entries are sorted by request start time and paginated, so if `offset + limit < total`, call the tool again with a higher offset to fetch the next page.

NameTypeRequiredDescription

organizationIDstringrequiredThe organization ID to run the query against. If not provided by the user, discover options using the list_organizations tool.

projectIDstringrequiredThe project ID to run the query against. If not provided by the user, discover options using the list_projects tool.

recordingIDstringrequiredThe recording ID of the session.

sessionIDintegerrequiredThe session ID of the session. Provide this as an integer.

endTimestringoptionalOptional ISO 8601 datetime. Only entries whose request started at or before this time are returned. Defaults to the end of the session.

limitintegeroptionalMaximum number of entries to return per call. Defaults to 100.

maxStatusintegeroptionalOptional inclusive upper bound on the response status code.

methodsarrayoptionalOptional list of HTTP methods (e.g., ["POST", "PUT"]). Only entries whose request used one of these methods are returned. Matching is case-insensitive.

minStatusintegeroptionalOptional inclusive lower bound on the response status code. Combine with maxStatus to select a range (e.g., 500 and 599 for server errors) or use both with the same value to select one code (e.g., 404).

offsetintegeroptionalNumber of matching entries to skip, for pagination. Defaults to 0.

startTimestringoptionalOptional ISO 8601 datetime. Only entries whose request started at or after this time are returned. Defaults to the start of the session.

urlFilterstringoptionalOptional case-insensitive substring filter applied to request URLs (e.g., "/api/cart" or "subdomain.example.com"). Only entries whose URL contains this substring are returned.

logrocketmcp_list_organizations#List all LogRocket organizations the authenticated user has access to. Use this first to discover available organizations before querying projects or sessions.0 params▾

List all LogRocket organizations the authenticated user has access to. Use this first to discover available organizations before querying projects or sessions.

logrocketmcp_list_projects#List all projects within a LogRocket organization. Use this to identify accessible projects before querying sessions, metrics, or issues.1 param▾

List all projects within a LogRocket organization. Use this to identify accessible projects before querying sessions, metrics, or issues.

NameTypeRequiredDescription

organizationSlugstringrequiredThe slug of the LogRocket organization. Use the list_organizations tool to find available organization slugs.

logrocketmcp_use_logrocket#Process a natural language query against LogRocket data — sessions, metrics, and issues. Use this to investigate user-reported bugs, understand behavior patterns, analyze performance metrics, and detect regressions by correlating code changes with LogRocket data.3 params▾

Process a natural language query against LogRocket data — sessions, metrics, and issues. Use this to investigate user-reported bugs, understand behavior patterns, analyze performance metrics, and detect regressions by correlating code changes with LogRocket data.

NameTypeRequiredDescription

organizationSlugstringrequiredThe slug of the LogRocket organization to query. Use the list_organizations tool to find available slugs.

projectSlugstringrequiredThe slug of the LogRocket project to query. Use the list_projects tool to find available slugs.

querystringrequiredNatural language query describing what to investigate. Examples: 'show me sessions where users encountered a checkout error', 'how many users hit the payment failure last week', 'find sessions with rage clicks on the signup button'.

logrocketmcp_watch_sessions#Use this to analyze one or more LogRocket sessions, each identified by its recording ID and session ID. You can use this tool to understand user behavior in the session or to extract additional information about the session (e.g., metadata, console logs, network requests and responses). Provide a separate natural language query describing what you want to know for each session to be analyzed. Sessions are analyzed in parallel, independently of each other. Session watching can take several minutes to complete; if pendingResults are returned, continue calling this tool with pollForResults: true and the pending fingerprints until all requests are complete.5 params▾

Use this to analyze one or more LogRocket sessions, each identified by its recording ID and session ID. You can use this tool to understand user behavior in the session or to extract additional information about the session (e.g., metadata, console logs, network requests and responses). Provide a separate natural language query describing what you want to know for each session to be analyzed. Sessions are analyzed in parallel, independently of each other. Session watching can take several minutes to complete; if pendingResults are returned, continue calling this tool with pollForResults: true and the pending fingerprints until all requests are complete.

NameTypeRequiredDescription

organizationIDstringrequiredThe organization ID to run the query against. If not provided by the user, discover options using the list_organizations tool.

projectIDstringrequiredThe project ID to run the query against. If not provided by the user, discover options using the list_projects tool.

fingerprintsarrayoptionalFingerprints identifying session watching requests that are still pending. Required when pollForResults is true.

pollForResultsbooleanoptionalSet to true to poll for completion of previously-submitted session watching requests. Omit in all other cases.

sessionsarrayoptionalSessions to be analyzed. Required when pollForResults is omitted or false. Omit when polling for already-submitted fingerprints.