LogRocket MCP honesty matrix — auto-open-PR marketing vs the published tool list
LogRocket MCP (docs.logrocket.com/docs/mcp) connects Cursor, Claude, and other MCP clients to session replays, metrics, and issues via Ask Galileo. The June 2, 2026 launch blog (blog.logrocket.com/introducing-the-logrocket-mcp) goes further: ShipStation CTO Nick Ciubotariu is quoted that when an issue surfaces, the agent "pulls the sessions, diagnoses the root cause, and opens a pull request automatically," and the same post describes an issue-resolution agent that "routes those issues to their coding agents to fix automatically."
The same docs page lists the published Tools — and they are LogRocket query/read surfaces: list_organizations, list_projects, use_logrocket, find_sessions, watch_sessions, get_network_entries, build_metric, find_issues. There is no create_pr, open_pr, codebase, or git write tool. Feedback DevTools is honest about a different surface: create_github_issue / create_tracker_issue plus source-mapped local-agent context with file:line. We do not claim server-side auto-opened or auto-merged PRs.
Feedback DevTools is our product. LogRocket MCP marketing sourced from blog.logrocket.com/introducing-the-logrocket-mcp (June 2, 2026); published Tools from docs.logrocket.com/docs/mcp; pricing from logrocket.com/pricing — lastChecked September 23, 2026 ~8am Asia/Jerusalem. Please verify before purchase.
Feedback DevTools vs LogRocket MCP
| Feedback DevTools | LogRocket MCP | |
|---|---|---|
| Marketing claim: opens a PR / fix automatically | No — FDT does not claim MCP ships fixes or opens PRs; local agent writes code from file:line context | Yes — blog (June 2, 2026): ShipStation CTO "opens a pull request automatically"; issue-resolution agent "routes those issues to their coding agents to fix automatically" |
| Published MCP tools (open-PR honesty) | get_feedback_context, list_open_feedback, list_clusters, create_github_issue, create_tracker_issue, mark_feedback_resolved… | list_organizations · list_projects · use_logrocket · find_sessions · watch_sessions · get_network_entries · build_metric · find_issues — query/read only; no create_pr / open_pr / codebase / git write |
| MCP tools that open GitHub / Linear tickets | Yes — create_github_issue (#57) + create_tracker_issue Linear (#59) with component + file:line in the body | No dedicated tracker-create / create_pr tools in the published list — tools query sessions, metrics, and issues |
| Open GitHub PR from MCP tool | No — create_github_issue + local-agent fix path (Cursor/Claude opens a PR if you ask; not a LogRocket-style MCP PR tool) | No dedicated create_pr / open_pr / git write tool — PR would be the coding agent using LogRocket session context |
| Auto-open / auto-merge PRs server-side | No — we do not claim server-side auto-opened or auto-merged PRs | No — marketing quotes automatic PR open / fix; published LogRocket MCP tools do not open or merge GitHub PRs |
| Source map on capture (component + file:line) | Yes — pinned at collect time for the local agent | Session replay, network HAR, metrics, issues + Ask Galileo diagnoses — rich product context, not React component file:line |
| Who applies the code fix | Your local Cursor / Claude agent (from MCP context or Claude Code prompt) | Your AI coding agent (Cursor, Claude Code, etc.) using LogRocket session/issue context — not a LogRocket-server PR opener |
| Query sessions / network / metrics from MCP | list_open_feedback / get_feedback_context (feedback items) | Yes — find_sessions, watch_sessions, get_network_entries, build_metric, use_logrocket, find_issues |
| List orgs / projects from MCP | N/A — project-scoped FDT MCP | Yes — list_organizations, list_projects |
| Free plan | Yes — unlimited feedback, forever | 14-day free trial; paid plans are session-quota based |
| Paid entry price | $9/mo per project (Pro) | Session-based (e.g. ~$176/mo at 25K sessions; seats/retention/add-ons vary) |
LogRocket MCP marketing quotes verified on blog.logrocket.com/introducing-the-logrocket-mcp (June 2, 2026); published Tools on docs.logrocket.com/docs/mcp; pricing on logrocket.com/pricing — lastChecked September 23, 2026 ~8am Asia/Jerusalem
Where LogRocket MCP is genuinely strong
Credit where due — LogRocket MCP is a real product-ops unlock if:
- You already capture LogRocket session replays and want Claude/Cursor to query sessions, network HAR, metrics, and issues without leaving the IDE.
- Ask Galileo (use_logrocket) chaining natural-language queries over sessions/metrics/issues matters more than React component file:line source maps.
- Your agents need org/project scoping (list_organizations / list_projects) and toolset filters (sessions, metrics, issues, ask-galileo).
- You want hosted MCP at mcp.logrocket.com/mcp with OAuth (or API-key) for Cursor / Claude / Codex / VS Code.
Where Feedback DevTools is different (honest foil)
- Marketing vs tools. The June 2, 2026 blog quotes "opens a pull request automatically" and "fix automatically"; the published Tools list is query-only — list_organizations, list_projects, use_logrocket, find_sessions, watch_sessions, get_network_entries, build_metric, find_issues — no create_pr / open_pr / codebase / git write (lastChecked September 23, 2026 ~8am Asia/Jerusalem). We quote both so buyers are not surprised.
- Tickets with file:line. create_github_issue and create_tracker_issue open GitHub/Linear tickets whose bodies carry component + file:line from capture. LogRocket's published list has no create_github_issue / create_pr equivalent.
- Local-agent path, not server-side PRs. Your Cursor/Claude agent applies the fix from FDT context. We do not claim to auto-open or auto-merge PRs on a server-side clone (contrast Usero request_ai_pr on /compare/usero-alternative). Distinct from Jam#69, Marker#68, BugHerd#67, Usero#66 / Usersnap strip.
- Capture-time source maps. Every item pins the React component and file path:line so the agent starts from a known path instead of rediscovering from session replay + network alone.
- Pricing shape. Unlimited free collection; Pro is $9/mo per project. LogRocket is session-quota priced (example ~$176/mo at 25K sessions) with MCP/API on Core+.
Pricing, side by side (as of September 23, 2026)
- Feedback DevTools: Free plan ($0, unlimited feedback) · Pro $9/mo per project
- LogRocket: Session-based Core/Pro/Enterprise (example ~$176/mo at 25K sessions; seats, retention, Streaming Export vary; MCP/API access on Core+; sources: logrocket.com/pricing; MCP docs: docs.logrocket.com/docs/mcp; blog: blog.logrocket.com/introducing-the-logrocket-mcp)
MCP honesty is about capability claims, not sticker shock — but one FDT Pro project is $9/mo vs LogRocket session-quota pricing that scales with traffic.
Who should choose what
- Choose LogRocket MCP if your product archive is LogRocket sessions/metrics/issues and you want agents to query replays, network HAR, and Ask Galileo without leaving the IDE.
- Choose Feedback DevTools if you want visual feedback with file:line on capture, MCP tools that create GitHub/Linear tickets, and a local-agent fix path — without reading "opens a pull request automatically" marketing as a published create_pr tool.
- Neither MCP is a silent auto-merge bot; both expect a human review step. The honest foil is what the published tools actually do. Distinct from Jam bug-to-fix marketing, Marker open-PR marketing, BugHerd codebase/CMS/design marketing, and Usero request_ai_pr.
Frequently asked questions
What does LogRocket MCP marketing claim?
Per blog.logrocket.com/introducing-the-logrocket-mcp (June 2, 2026; lastChecked September 23, 2026 ~8am Asia/Jerusalem): ShipStation CTO Nick Ciubotariu is quoted that the agent "pulls the sessions, diagnoses the root cause, and opens a pull request automatically." The same post describes "An issue resolution agent that watches user sessions, surfaces usability and technical problems, and routes those issues to their coding agents to fix automatically."
What tools does LogRocket MCP actually publish?
The Tools section on docs.logrocket.com/docs/mcp lists query/read tools: list_organizations, list_projects, use_logrocket (Ask Galileo NL queries), find_sessions, watch_sessions, get_network_entries (HAR), build_metric, find_issues. Toolsets can scope to sessions, metrics, issues, ask-galileo, or all. Those load LogRocket data — they are not create_pr, open_pr, codebase, or git write tools.
Does LogRocket MCP open pull requests?
Marketing language (ShipStation CTO quote + "fix automatically" agent example) implies agents that open PRs / ship fixes, but the published tool list has no create_pr / open_pr / GitHub write tool (lastChecked September 23, 2026 ~8am Asia/Jerusalem). A PR, if any, is the coding agent's git workflow using LogRocket session context — not a LogRocket MCP PR tool.
Does Feedback DevTools auto-open or auto-merge GitHub PRs server-side?
No. Feedback DevTools MCP creates tracker tickets (create_github_issue, create_tracker_issue for Linear) and supplies source-mapped context / Claude Code prompts so your local agent can write the fix. We do not claim to auto-open or auto-merge pull requests server-side.
How does Feedback DevTools MCP foil LogRocket MCP?
FDT is honest about a different surface: capture-time component + file:line, create_github_issue / create_tracker_issue, and a local-agent path. LogRocket MCP is strong at piping session/metrics/issue context into the agent. Marketing that implies automatic PR open or auto-fix should be read against the published Tools list on docs.logrocket.com/docs/mcp.
Collect source-mapped feedback and open GitHub/Linear tickets from MCP — free.