Can my team share one Fullstory connection?

Yes. One person connects Fullstory in Elaichi and shares the connection with a team, and nobody else ever handles a credential. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who computed a metric or opened a session, not the person who connected the account.

Analytics

Fullstory MCP connector

The Fullstory connector brings sessions, segments, metrics, funnels and journeys into Claude, ChatGPT, Cursor and the Elaichi Agent, so each person can ask about user behavior in plain language inside their own Fullstory access.

Connect on Elaichi How to connect

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.

33 tools

How to connect

How to connect Fullstory to Claude, ChatGPT or Cursor

Two steps, about a minute.

In Elaichi

Connect Fullstory once

Open Connections, choose Add connection, and pick Fullstory.
Optionally set Share with to give a team access, then press Connect.
Approve it in Fullstory. Fullstory'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.

fullstory

All categories

Fullstory

Allium

Amplitude

Artie

AthenaHQ

Botify

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.

Fullstory 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.

Fullstory 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.

Fullstory 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 Fullstory 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.

Connect Fullstory on Elaichi See pricing

Use cases

What teams do with Fullstory through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

Product

Find where users drop off in a flow

Build a funnel for the new checkout steps, compute it, and pull the sessions where people abandoned, all from a question typed in plain language.
Design

Watch the sessions behind a confusing screen

Ask for the sessions matching a segment, open one, take a screenshot or compare two states, and see exactly what the person saw.
Support

See what a customer did before writing in

Build a segment for the account that reported a bug and open the sessions behind the ticket, without asking the customer to reproduce anything.
Marketing

Check whether a campaign page converts

Compute view counts and a funnel from landing page to signup for a campaign segment, and get the result summarized in the chat.
Engineering

Measure the impact of a release

Define a metric for errors or rage clicks, compute it before and after a deploy, and pull the sessions that triggered it to see what broke.
Analytics

Keep segments and metrics up to date

Update a segment's rules or a metric's definition from a short request, then recompute it to confirm the numbers moved the way you expected.

Try asking

“Compute the checkout funnel for last week and show drop-off.”
“Show sessions from the enterprise segment with rage clicks this week.”
“Build a metric for signups from the pricing page.”

See all 33 Fullstory tools below

Compare

Elaichi vs Zapier MCP vs Composio for Fullstory

All three can connect Fullstory 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 Fullstory, 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 Fullstory tools	Allow or restrict single Fullstory 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 Fullstory 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

Fullstory tools for your AI agents

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

See it in Elaichi

What connecting Fullstory gets you

6 screens from the product, each doing one job for your Fullstory account.

The agent

Ask Fullstory questions in plain language.

Compute a funnel, pull the sessions behind it, and read the answer in chat.

sessions
segments
metrics
funnels

Ask Elaichi to work across your apps.

Compute the checkout funnel for last week and show drop-off.

Show sessions from the enterprise segment with rage clicks this week.

Build a metric for signups from the pricing page.

Also runs in Claude, ChatGPT or Cursor

MCP clients

One endpoint for Claude, ChatGPT and Cursor.

Connect Fullstory once and every MCP client works through it, no SDK, no shared key.

ElaichiMCP clients

Claude

ChatGPT

Cursor

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

Tool catalog

33 Fullstory tools, no code to write.

Sessions, segments, metrics, funnels and journeys covered from the day you connect.

Session open
Session screenshot
Session get a11y tree
Session diff

ElaichiTools

Tool	Action	Description
Session open	Open	Open a Fullstory session for visual inspection. Pass device_id and session_id (from the session replay URL). Returns a client_id plus event summaries you can use to choose interesting timestamps.
Session screenshot	Action	Render a screenshot for an open session at a given page_id and timestamp. Use this to see what the user saw at a moment of interest. Sequential calls with increasing timestamps are faster than random access.
Session get a11y tree	Get	Get the accessibility tree for an open session at a given page_id and timestamp. Use this to inspect element structure (roles, labels, hierarchy). Sequential calls with increasing timestamps are faster than random access.
Session diff	Action	Diff the accessibility tree of an open session between two timestamps on a page. Returns a text summary of accessibility tree changes. Use this to find what changed when something broke.
Session close	Close	Required. Close an open session and free associated resources. Always call this when you're done investigating a session — open sessions hold server-side resources, and failing to close them may block further session_open calls.

Toolboxes

Every team gets its own Fullstory toolbox.

Product computes funnels, Support opens sessions, each team scoped to what it needs.

Product
Design
Support
Marketing

ElaichiToolboxes

Name	Source template	Tools	Created
Product toolbox Fullstory · funnels and journeys	Fullstory starter	18	Mar 4, 2026
Design toolbox Fullstory · sessions and screenshots	—	9	Mar 2, 2026
Support toolbox Fullstory · customer sessions	—	24	Feb 27, 2026
Marketing toolbox Fullstory · segments and view counts	Fullstory starter	6	Feb 19, 2026
Engineering toolbox Fullstory · error metrics and release impact	—	31	Jan 30, 2026
Analytics toolbox Fullstory · metrics and segments	—	12	Jan 22, 2026

Shared connections

Share a Fullstory connection without sharing credentials.

One person connects, teams and members work through it, and nobody sees a secret.

Product Web
Mobile App
Support
Growth

ElaichiConnections

Connection	Scope	Status	Access
FU Fullstory (Product Web) Connected by Emily Carter	Personal	• Active	1 team · 6 members
FU Fullstory (Mobile App) Connected by Jake Morgan	Organization	• Active	3 teams · 24 members
FU Fullstory (Support) Connected by Megan Brooks	Organization	• Active	2 teams · 11 members
FU Fullstory (Growth) Connected by Tyler Reed	Personal	• Needs re-auth	1 team · 3 members
FU Fullstory (Design) Connected by Ryan Hayes	Personal	• Active	Not shared
FU Fullstory (Analytics) Connected by Ashley Parker	Personal	• Active	2 teams · 9 members

Audit log

Every Fullstory call lands in the audit log.

Who computed which metric, opened which session and when, answered in one table.

When
Who
What happened
Type

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]	Fullstory Users Updated	MCP
26 minutes ago Mar 6, 2026, 2:46 PM	R Ryan Hayes [email protected]	Fullstory Sessions Created	MCP
32 minutes ago Mar 6, 2026, 2:40 PM	A Ashley Parker [email protected]	Fullstory Sessions List	Toolbox

Launching 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, a person approves.

Fetch Fullstory sessions, group them, draft a digest, approve it, post it back.

Fullstory digest

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

Run now

✓

Schedule

Every weekday at 8:00 AM

0.2s
✓

Fetch sessions

Fullstory

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

Fullstory

Queued

Collections and dashboards

Fullstory health numbers, computed with no model.

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

Fullstory health

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

Live

Sessions

1,284 ↓ 12%

Segments

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Sessions created

Last 14 days

By team

Share of activity

Product Web 34%

Mobile App 27%

Support 21%

Growth 18%

Related connectors

More from the catalog

Browse all 600+ connectors →

FAQ

Frequently asked questions

How do I connect Fullstory to Claude?

Connect Fullstory in Elaichi first by signing in through Fullstory's own OAuth prompt, with no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and your Fullstory sessions, segments, metrics, funnels and journeys are available in the chat.

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

Yes. The Fullstory connection you make in Elaichi is reached through the same endpoint, https://api.elaichi.ai/mcp, from Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent. You connect Fullstory once and every client you use gets it.

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

It can build and update segments, metrics, funnels and journeys in Fullstory, compute them, and pull the sessions behind a funnel or journey step. It can also open a session, take a screenshot, read the accessibility tree and compare two states so you can see what a user saw. Short, concrete asks such as "compute the checkout funnel for last week" work better than long sentences.

Does connecting Fullstory give the AI everything in my Fullstory org?

No. Every call to Fullstory runs as the person who signed in, so the AI can only reach the segments, metrics, funnels, journeys and sessions that person can already see in Fullstory. Elaichi can narrow that access further with roles and restrictions, and it can never widen it beyond what Fullstory itself allows.

Can I stop an agent from changing things in Fullstory?

Yes. Restrictions in Elaichi work per action, so you can allow computing segments, metrics and funnels in Fullstory while blocking updates to their definitions. A restricted action is never advertised to the AI client at all, so no prompt, however worded, can reach it.

What happens to a Fullstory connection when someone leaves?

Offboarding a person in Elaichi ends their access to Fullstory through every client at once. A Fullstory connection they shared keeps working for everyone else on the team. If you later disconnect Fullstory in Elaichi, it is removed from Claude, ChatGPT, Cursor and every other client in one step.

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

Yes. Fullstory 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 Fullstory?

Yes. Both let Claude, ChatGPT or Cursor use Fullstory. 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 Fullstory call.

How is Elaichi different from Composio for Fullstory?

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 Fullstory: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Fullstory in front of your team

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

Connect Fullstory Talk to us

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.