Fullstory MCP connector
The Fullstory connector brings sessions, segments, metrics, funnels and journeys into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person can ask about user behavior in plain language inside their own Fullstory access.
- Connects over OAuth
- Free 14-day trial
- No credit card
Regions: US and EU. Elaichi supports all of them; you pick your region when you connect.
Compute the checkout funnel for last week and show drop-off.
Working in Fullstory with Elaichi
-
Session get a11y tree
-
Get segment
-
Get metric
How to connect Fullstory to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
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 Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
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.
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. 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.
Fullstory MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
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 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.
What teams do with Fullstory through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Fullstory is logged.
-
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.”
What connecting Fullstory gets you
6 screens from Elaichi, each doing one job for your Fullstory account.
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, Cursor or Microsoft Copilot
The agent
Ask Fullstory questions in plain language.
Compute a funnel, pull the sessions behind it, and read the answer in chat.
Copy the endpoint
AI apps
One endpoint for Claude, ChatGPT, Cursor and Microsoft Copilot.
Connect Fullstory once and every MCP client works through it, no SDK, no shared key.
Tool catalog
33 Fullstory tools, no code to write.
Sessions, segments, metrics, funnels and journeys covered from the day you connect.
Toolboxes
Every team gets its own Fullstory toolbox.
Product computes funnels, Support opens sessions, each team scoped to what it needs.
Shared connections
Share a Fullstory connection without sharing credentials.
One person connects, teams and members work through it, and nobody sees a secret.
Audit log
Every Fullstory call lands in the audit log.
Who computed which metric, opened which session and when, answered in one table.
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.
Fullstory digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
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 Jake Morgan
Approve Deny -
Post the digest
Fullstory
Queued
Workflows
A schedule starts the work, a person approves.
Fetch Fullstory sessions, group them, draft a digest, approve it, post it back.
Fullstory health
Refreshed 4 minutes ago · every 15 minutes · from the sessions collection
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%
Collections and dashboards
Fullstory health numbers, computed with no model.
Four metrics, 14 days of segments created and a team breakdown, refreshed on schedule.
Why connect Fullstory's MCP server through Elaichi
Fullstory builds and runs this MCP server. Elaichi sits in front of it, so Fullstory'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 Fullstory's server directly, outside Elaichi, get none of this.
-
One address for every AI client
Claude, ChatGPT, Cursor and Microsoft Copilot reach Fullstory's tools at the same Elaichi address as every other connected app. Nobody adds Fullstory'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 Fullstory 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 Fullstory's server. By default, a tool Fullstory 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 Fullstory
Fullstory builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Fullstory team.
For IT and engineering
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.
| 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 | 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.
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.
No tools match your search.
Questions, answered
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, Microsoft Copilot, 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 restricting updates to their definitions. A restricted action still appears in Elaichi's tool search, flagged as restricted, but the AI client cannot run it, whatever the prompt says.
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, Microsoft Copilot 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, 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 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 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