Fullstory (EU) MCP connector
Fullstory (EU) connects your EU-hosted session replays, segments, funnels, metrics and journeys to Claude, ChatGPT, Cursor and the Elaichi Agent, so your team can ask about user behavior in plain language inside their own Fullstory access.
-
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.
How to connect
How to connect Fullstory (EU) to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Fullstory (EU) once
-
Open Connections, choose Add connection, and pick Fullstory (EU).
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Fullstory (EU). Fullstory (EU)'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.
Fullstory (EU) 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 (EU) 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 (EU) 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 (EU) 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 Fullstory (EU) 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 out of checkout
Build a funnel in Fullstory (EU) from first page to purchase, compute it for the week, and pull up the sessions of people who left at the step that hurts most.
-
UX research
Watch the sessions behind a confusing screen
Open a session, take a screenshot of the moment someone got stuck, and compare two sessions to see what was different for the person who gave up.
-
Support
See what a customer did before writing in
Build a segment that matches the customer's path, open the sessions it returns, and answer the ticket with what actually happened on the page.
-
Marketing
Check how a campaign landing page performs
Build a metric for view counts on the campaign page in Fullstory (EU), compute it for this week, and update it when the page changes.
-
Engineering
Check accessibility on a live page
Open a session and read the accessibility tree to find unlabeled buttons, missing alt text and focus traps before the next release goes out.
-
Growth
Map the journey from first visit to upgrade
Build a journey across the pages that lead to an upgrade, compute it to see the paths people really take, and open the sessions behind the ones that stall.
Try asking
- “Which checkout funnel step lost the most users this week?”
- “Open the sessions behind yesterday's failed signups and screenshot them.”
- “Compare the mobile and desktop segments on the pricing page.”
Compare
Elaichi vs Zapier MCP vs Composio for Fullstory (EU)
All three can connect Fullstory (EU) 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 (EU) tools | Allow or restrict single Fullstory (EU) 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 (EU) 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 (EU) tools for your AI agents
33 tools are ready to call through Elaichi's MCP endpoint the moment you connect Fullstory (EU), governed by the same roles, restrictions, and audit log as everything else in Elaichi. Fullstory (EU) builds and runs these tools.
No tools match your search.
See it in Elaichi
What connecting Fullstory (EU) gets you
6 screens from the product, each doing one job for your Fullstory (EU) account.
The agent
Ask Fullstory (EU) what users actually did.
Get answers from live sessions, funnels and metrics in plain language.
- sessions
- segments
- funnels
- journeys
Ask Elaichi to work across your apps.
Which checkout funnel step lost the most users this week?
Open the sessions behind yesterday's failed signups and screenshot them.
Compare the mobile and desktop segments on the pricing page.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One governed endpoint for every MCP client.
Use Fullstory (EU) from Claude, ChatGPT or Cursor with no SDK and no shared API key.
Copy the endpoint
Tool catalog
33 Fullstory (EU) tools, no code to write.
Sessions, segments, metrics, funnels and journeys covered without building a connector yourself.
- Session open
- Session screenshot
- Session get a11y tree
- Session diff
Toolboxes
Every team gets its own Fullstory (EU) toolbox.
Product, Support and Marketing each see the tools their work needs.
- Product
- UX research
- Support
- Marketing
Shared connections
Share a Fullstory (EU) connection, not a credential.
Teammates work through one connection and never see a token or password.
- Product
- UX research
- Support
- Marketing
Audit log
Every Fullstory (EU) call is on record.
See who opened which session or changed which funnel, and when.
- When
- Who
- What happened
- Type
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 (EU) sessions weekly, group them, draft a digest, approve, then post it back.
Fullstory (EU) digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch sessions
Fullstory (EU)
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 (EU)
Queued
Collections and dashboards
Fullstory (EU) health, computed without a model.
Four metrics, 14 days of sessions created and a team breakdown, refreshed on schedule.
Fullstory (EU) 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 34%
UX research 27%
Support 21%
Marketing 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Fullstory (EU) to Claude?
In Elaichi, choose Fullstory (EU), which is the EU deployment of Fullstory, and sign in to Fullstory in EU with your usual account over OAuth. There is 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. Your Fullstory (EU) sessions, segments, funnels and metrics are then available in Claude as you.
Does Fullstory (EU) work with ChatGPT and Cursor as well as Claude?
Yes. Fullstory in EU is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You do not connect Fullstory (EU) again for each client.
What can an AI agent actually do with my Fullstory (EU) data?
With Fullstory in EU connected, an agent can open a session replay, take a screenshot of a moment in it, read the page's accessibility tree and compare two sessions. It can also build, update and compute segments, metrics, funnels and journeys, check view counts for a page, and pull the sessions behind a funnel step or a journey path. Short, concrete asks such as "compute the checkout funnel for last week" work better than long paragraphs.
Does connecting Fullstory (EU) give the AI access to everything in my Fullstory account?
No. Every request to Fullstory in EU runs as the person who signed in, so an agent sees only the sessions, segments and funnels that person could already see in Fullstory (EU). Elaichi can narrow that access further with roles and restrictions, and it can never widen it beyond what Fullstory already allows.
Can I stop an agent from changing segments, funnels or metrics in Fullstory (EU)?
Yes. Restrictions in Elaichi work per action, so you can allow reading and computing in Fullstory in EU while blocking updates to segments, funnels, metrics or journeys. A restricted action is never advertised to Claude, ChatGPT, Cursor or any other client, so no prompt can reach it.
What happens to a Fullstory (EU) connection when someone leaves?
Offboarding a person in Elaichi ends their access to Fullstory in EU at once, across every client they used. A shared Fullstory (EU) connection keeps working for everyone else on the team. Disconnecting Fullstory (EU) once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.
Does the Fullstory (EU) MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Fullstory (EU) 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 (EU)?
Yes. Both let Claude, ChatGPT or Cursor use Fullstory (EU). 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 (EU) call.
How is Elaichi different from Composio for Fullstory (EU)?
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 (EU): 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 (EU) 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.