Aleph
Query live FP&A data, build reports and update dashboards from your AI assistant.
LogRocket
Query LogRocket sessions, issues and metrics from an AI agent for debugging.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
What the LogRocket connector does
The LogRocket MCP server connects session replay and product analytics to Claude and any MCP-compatible agent. Its seven tools find sessions and issues, read organizations and projects, and build metrics — so an agent debugging a bug report can look at what actually happened rather than guess.
Connection verified
Connection checked by Agentman on .
Listed in Anthropic’s Connectors Directory at community tier — a listing, not a partner-level review.
Anthropic states this reflects the level of review a connector received, not a security audit.
LogRocket tools (7)
- build_metric
- find_issues
- find_sessions
- list_organizations
- list_projects
- use_logrocket
- watch_sessions
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Read-only surface, sensitive data. Nothing published here writes, but session replay can contain user input and PII — the risk on this connector is exposure, not destruction.
- The RFC 9728 descriptor advertises no scopes, so there is no documented way to narrow the grant below what the account can see.
- No rate limits are published for the MCP server that we could find, so none are stated here.
- Session and issue coverage depends on your LogRocket plan and retention, which this connector does not change; a session outside retention is not reachable by any tool.
- We did not read tool schemas. The endpoint requires OAuth, so names come from Anthropic's directory and behaviour from LogRocket's documentation. We exercised no tool.
Frequently asked questions
What is the LogRocket MCP server actually for?
Debugging with real session evidence instead of guesses. LogRocket describes it as letting Cursor, Claude Code, Codex and other clients query the LogRocket API about sessions, metrics and issues, so an agent can pull context about how your app behaved, understand how users interact with a feature, and investigate a specific user or account's sessions.
Can the LogRocket MCP server change anything in my account?
Nothing in the listed tool set writes. All seven tools read or build queries: listing organizations and projects, finding sessions and issues, watching sessions, and building a metric. LogRocket frames the server as querying the LogRocket API for information, and publishes no write or delete tool in this surface.
Do I need to name a LogRocket project before querying?
In practice yes, and two tools exist for it. list_organizations and list_projects enumerate what your account can reach, which is how an agent resolves the right project before calling find_sessions or find_issues. The use_logrocket tool is the documented entry point for orienting an agent in the workflow.
What kind of prompts work with the LogRocket MCP server?
LogRocket publishes several. Its examples include asking an agent to watch a specific user's sessions to find a checkout root cause, to explain how a feature is currently used before you change it, to triage the past week's new issues by root cause, and to check whether last week's commits introduced regressions.
Does the LogRocket MCP server need an API key?
No, it uses OAuth. We confirmed the server issues an HTTP 401 with a Bearer challenge carrying realm OAuth, and publishes RFC 9728 metadata naming itself as the authorization server. There is no API key to paste into a client config, and the sign-in happens in the browser.
Can an agent see session data for users I cannot access?
No. The connector reaches what your LogRocket account reaches, and list_organizations and list_projects exist precisely to enumerate that scope. LogRocket publishes no documented mechanism for the MCP server to widen access beyond the authenticated user's own organizations and projects, and the server advertises no OAuth scopes that would narrow it either.
Sources
- LogRocket MCP server documentation (read as Markdown via the
.mdvariant LogRocket publishes for AI agents, named in itsllms.txtindex; retrieved 2026-09-13), source of the example prompts quoted above · retrieved 2026-09-13 - Live OAuth posture check against
https://mcp.logrocket.com/mcp— HTTP 401 with awww-authenticateBearer challenge carryingrealm="OAuth", and RFC 9728 metadata athttps://mcp.logrocket.com/.well-known/oauth-protected-resource/mcpnaminghttps://mcp.logrocket.comas the authorization server (2026-09-13) · retrieved 2026-09-13 - Anthropic Connectors Directory entry (retrieved 2026-09-13) · retrieved 2026-09-13
- LogRocket support — · Privacy
More Analytics connectors
august
Interview simulated customer twins, run focus groups and surveys from an AI agent.
ChartMogul
Query MRR, ARR, churn, retention, cohorts, customers and sales pipeline from your AI assistant.
Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.
Use it in an agent
Put LogRocket to work.
Connect LogRocket once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.