Skip to content

LogRocket MCP connector

The LogRocket connector brings session replays, issues, network requests and metrics into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so your team can ask about what users actually saw and did.

  • Connects over OAuth
  • Free 14-day trial
  • No credit card
ChatGPT Elaichi connected

Find sessions from acme.com this week that hit a checkout error

Working in LogRocket with Elaichi

  • List organizations
  • List projects
  • Get network entries
Ask anything…
Governance / Audit log Last 24 hours
LogRocket Get network entries Emily Carter · ChatGPT · 9:41 AM Done
LogRocket List projects Emily Carter · ChatGPT · 9:41 AM Done
LogRocket List organizations Emily Carter · ChatGPT · 9:41 AM Done
LogRocket Use LogRocket Megan Brooks · Claude · 9:38 AM Done
LogRocket Find sessions Ryan Hayes · Cursor · 9:35 AM Done

How to connect LogRocket to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

LogRocket MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

LogRocket MCP connector for Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

    https://api.elaichi.ai/mcp
  2. 2

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

LogRocket MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

LogRocket MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

LogRocket MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

    https://api.elaichi.ai/mcp
  3. 3

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect LogRocket to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

What teams do with LogRocket through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in LogRocket is logged.

  • Support

    Find the session behind a ticket

    A customer says checkout broke on Tuesday. Ask for their sessions from that day, open the one with the error, and watch exactly what they saw before writing back.

  • Product

    Check whether a new issue is spreading

    Ask which issues in the web app project appeared this week and how many sessions each one touched, then decide what goes into the next sprint.

  • Engineering

    Trace a failed request without leaving the editor

    From Cursor, ask for the network entries in a broken session and see which request failed, what it returned, and how long it took.

  • QA

    Confirm a bug is really fixed after release

    After a deploy, ask for sessions on the new version that hit the old error. An empty answer is the sign-off you were looking for.

  • Customer success

    Prepare for a renewal call with real usage

    Ask for recent sessions from the account, see which parts of the product they visit and where they get stuck, and walk into the call knowing what to raise.

  • Design

    See where people stall in a new flow

    Build a metric for how many sessions reach the last step of onboarding versus drop off, and watch a few of the sessions that gave up.

Try asking

  • “Find sessions from acme.com this week that hit a checkout error”
  • “Which issues in the web app project are new since Monday?”
  • “Show the failed network requests in the session from ticket 4821”

See all 8 LogRocket tools →

What connecting LogRocket gets you

6 screens from Elaichi, each doing one job for your LogRocket account.

Elaichi Agent

Ask Elaichi to work across your apps.

Find sessions from acme.com this week that hit a checkout error

Which issues in the web app project are new since Monday?

Show the failed network requests in the session from ticket 4821

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask what a user saw, get the session.

Ask the Elaichi Agent in plain language and get answers from live LogRocket sessions and issues.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

One endpoint reaches LogRocket from every client.

Claude, ChatGPT, Cursor and Microsoft Copilot connect through one org endpoint, no SDK and no shared key.

ElaichiTools
Tool Action Description
List organizations List For listing the LogRocket organizations you can access. Hidden when scoping to a specific organization (e.g., https://mcp.logrocket.com/mcp/<your_organization_id>).
List projects List For listing the LogRocket projects you can access within a given organization. Hidden when scoping to a specific project (e.g., https://mcp.logrocket.com/mcp/<your_organization_id>/<your_project_id>).
Use LogRocket Action For running natural language queries against your LogRocket data (e.g., sessions, metrics, and issues). Queries are handled by Ask Galileo which chains tool calls internally.
Find sessions Action For filtering LogRocket sessions.
Watch sessions Action For analyzing and/or extracting additional information about one or more sessions.

Tool catalog

8 LogRocket tools, no code to write.

Sessions, issues, network entries, metrics and projects are covered without a line of custom code.

ElaichiToolboxes
Name Source template Tools Created

Support toolbox

LogRocket · customer sessions and errors

LogRocket starter 18 Mar 4, 2026

Product toolbox

LogRocket · issues and metrics

— 9 Mar 2, 2026

Engineering toolbox

LogRocket · sessions and network entries

— 24 Feb 27, 2026

QA toolbox

LogRocket · release issues

LogRocket starter 6 Feb 19, 2026

Customer success toolbox

LogRocket · account sessions

— 31 Jan 30, 2026

Design toolbox

LogRocket · flows and drop-off metrics

— 12 Jan 22, 2026

Toolboxes

Every team gets its own LogRocket toolbox.

Support, Product and Engineering each get a toolbox scoped to the work they do.

ElaichiConnections
Connection Scope Status Access
LO

LogRocket (Support)

Connected by Emily Carter

Personal • Active 1 team · 6 members
LO

LogRocket (Product)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
LO

LogRocket (Engineering)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
LO

LogRocket (QA)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
LO

LogRocket (Customer success)

Connected by Ryan Hayes

Personal • Active Not shared
LO

LogRocket (Mobile app)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Teammates use the connection, never the credential.

One person connects LogRocket, shares it with a team, and nobody else handles a credential.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

LogRocket Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

LogRocket Sessions Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

LogRocket Sessions List Toolbox

Audit log

Every LogRocket call is on the record.

When, who, what happened and which session or issue, in an append-only log.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.

LogRocket digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch sessions

    LogRocket

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    LogRocket

    Queued

Workflows

A schedule starts the work, not a question.

New LogRocket issues are fetched, grouped, drafted into a digest, approved, then posted back.

LogRocket health

Refreshed 4 minutes ago · every 15 minutes · from the sessions collection

Live

Sessions

1,284 ↓ 12%

Issues

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Sessions created

Last 14 days

By team

Share of activity

Support 34%

Product 27%

Engineering 21%

QA 18%

Collections and dashboards

Numbers from LogRocket, no model in the math.

Four metrics, 14 days of sessions created, and a team breakdown, refreshed on a schedule.

Why connect LogRocket's MCP server through Elaichi

LogRocket builds and runs this MCP server. Elaichi sits in front of it, so LogRocket's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to LogRocket's server directly, outside Elaichi, get none of this.

  • One address for every AI client

    Claude, ChatGPT, Cursor and Microsoft Copilot reach LogRocket's tools at the same Elaichi address as every other connected app. Nobody adds LogRocket's server to each client one by one.

  • Each person signs in as themselves

    Each person signs in to Elaichi as themselves. Members connect with their own LogRocket sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.

  • Rules checked before a call leaves

    Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches LogRocket's server. By default, a tool LogRocket does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.

  • One audit log for every app

    Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.

  • Tool issues go to LogRocket

    LogRocket builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the LogRocket team.

    logrocket.com/contact

Why run a vendor's MCP server through Elaichi →

For IT and engineering

Elaichi vs Zapier MCP vs Composio for LogRocket

All three can connect LogRocket to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for LogRocket, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over LogRocket tools Allow or restrict single LogRocket tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per LogRocket call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price Free for one person; $15 per user per month on Gold. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

LogRocket tools for your AI agents

8 tools are ready to call through Elaichi's MCP endpoint the moment you connect LogRocket, governed by the same roles, restrictions, and audit log as everything else in Elaichi. LogRocket builds and runs these tools.

Questions, answered

How do I connect LogRocket to Claude?

Connect LogRocket in Elaichi first: pick it from the catalog and sign in to LogRocket over OAuth, the same way you sign in to the LogRocket website. There is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Claude asks you to sign in to Elaichi once and LogRocket is available from then on.

Does LogRocket work with ChatGPT and Cursor as well as Claude?

Yes. Once LogRocket is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. You connect LogRocket once and every client picks it up.

What can an AI agent actually do with my LogRocket data?

With LogRocket connected, an agent can list your organizations and projects, find sessions for a user, an account or a date range, watch what happened in a session, pull the network requests behind it, look up issues, and build a metric across sessions. In practice that means asking things like "show me the sessions from acme.com that hit an error this week" and getting back real LogRocket results. Short, specific asks work better than long paragraphs.

Does connecting LogRocket give the AI access to every project?

No. Every call to LogRocket runs as the person who signed in, so the AI sees only the organizations and projects that person can already open in LogRocket. Elaichi can narrow that further, for example to a single project or to read-only work, but it can never widen it beyond what the person has in LogRocket.

Can my team share one LogRocket connection?

Yes. One person connects LogRocket in Elaichi and shares the connection with a team, and nobody else on the team ever handles a credential. Each person still signs in to Elaichi as themselves, so every LogRocket session they open or issue they look up is logged under their own name.

Can I stop an agent from changing things in LogRocket?

Yes. Restrictions in Elaichi apply per action, so you can allow finding and watching LogRocket sessions while restricting anything you do not want an agent to touch. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.

What happens to a LogRocket connection when someone leaves?

Offboarding a person in Elaichi ends their access to LogRocket through every client at once, with nothing to revoke in Claude, ChatGPT, Cursor or Microsoft Copilot separately. A LogRocket connection shared with a team keeps working for everyone else. If you want LogRocket gone entirely, disconnecting it once in Elaichi removes it from every client.

Does the LogRocket MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. LogRocket is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for LogRocket?

Yes. Both let Claude, ChatGPT or Cursor use LogRocket. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every LogRocket call.

How is Elaichi different from Composio for LogRocket?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to LogRocket: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put LogRocket in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot