Which AI clients can use the LogRocket MCP server?

27 AI clients, including Cursor, VS Code, and Claude. Each connects to LogRocket as a remote MCP server through Runlayer, which adds identity, policy, scanning, and audit to every call.

Which LogRocket tools are available?

LogRocket exposes 3 tools, including List organizations, List projects, Use LogRocket. Admins choose which ones each group can call.

How does LogRocket authenticate?

Sign in the way LogRocket requires. Runlayer holds the credentials so they stay out of the client’s configuration.

Integrations / MCP servers

LogRocket

Query LogRocket session replays, issues, metrics, and user behavior for debugging

Book a demo View documentation

Tools

3 available tools

Search the tool definitions captured from the MCP server. The live list can vary with version, deployment, and credentials.

Search 3 tools

List organizations
Tool name: list_organizations
List organizations the user has access to.
List projects
Tool name: list_projects
List projects the user has access to.
Use LogRocket
Tool name: use_logrocket
Run a natural language query against LogRocket.

Compatibility

Connect LogRocket to the clients your teams already use

27 AI clients can connect to LogRocket through Runlayer. Pick one for its setup steps and controls.

Why Runlayer

Why connect LogRocket through Runlayer?

One approved path

Approve LogRocket once and everyone gets it in the AI clients they already use. Runlayer holds the credentials, so nothing sits in client configuration.

Fine-grained policy

Control who can use each server, tool, and resource, and under which runtime conditions.

Runtime security

Scan tool inputs and outputs for prompt injection, credential exposure, PII, and data exfiltration, then alert, mask, or block.

Audit and observability

Trace every request across users, clients, tools, policies, scanner decisions, and downstream systems.