LogRocket MCP connector
The LogRocket connector brings session replays, issues, network requests and metrics into Claude, ChatGPT, Cursor and the Elaichi Agent, so your team can ask about what users actually saw and did.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
8 tools
How to connect
How to connect LogRocket to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect LogRocket once
-
Open Connections, choose Add connection, and pick LogRocket.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in LogRocket. LogRocket's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
LogRocket MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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 ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
LogRocket MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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.
Connect LogRocket to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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.
Use cases
What teams do with LogRocket through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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”
Compare
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.
| 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 | $15 per user per month. | 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.
AI tools
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.
No tools match your search.
See it in Elaichi
What connecting LogRocket gets you
6 screens from the product, each doing one job for your LogRocket account.
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.
- sessions
- issues
- projects
- network entries
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 or Cursor
MCP clients
One endpoint reaches LogRocket from every client.
Claude, ChatGPT and Cursor connect through one org endpoint, no SDK and no shared key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
8 LogRocket tools, no code to write.
Sessions, issues, network entries, metrics and projects are covered without a line of custom code.
- List organizations
- List projects
- Use LogRocket
- Find sessions
ElaichiToolsToolboxes
Every team gets its own LogRocket toolbox.
Support, Product and Engineering each get a toolbox scoped to the work they do.
- Support
- Product
- Engineering
- QA
ElaichiToolboxesShared connections
Teammates use the connection, never the credential.
One person connects LogRocket, shares it with a team, and nobody else handles a credential.
- Support
- Product
- Engineering
- QA
ElaichiConnectionsAudit log
Every LogRocket call is on the record.
When, who, what happened and which session or issue, in an append-only log.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule starts the work, not a question.
New LogRocket issues are fetched, grouped, drafted into a digest, approved, then posted back.
LogRocket digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch sessions
LogRocket
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
LogRocket
Queued
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.
LogRocket health
Refreshed 4 minutes ago · every 15 minutes · from the sessions collection
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%
FAQ
Frequently asked questions
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, 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 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 blocking anything you do not want an agent to touch. A restricted action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt, however clever, can reach it.
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 or Cursor 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, 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 on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.