Resources · Claude connector

Claude Fullstory connectorWhat Claude can do in your Fullstory account.

The Claude Fullstory connector exposes 29 tools. 21 read, 8 write, 0 left undocumented. Claude turns plain questions into segments, metrics, funnels and journeys, then opens the real sessions behind the numbers. Here: what it saves, what it cannot touch, and what admins must switch on.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What changes for product and UX teams

Fullstory already records how people use your product. The connector lets you question that data in plain language: Claude defines the cohort, computes the number, explains it, and then opens actual user sessions so a drop in conversion comes with the reason, not just the percentage.

Find where checkout leaks. A product manager describes the purchase path in a sentence. build_funnel saves it as a funnel, compute_funnel returns conversion at every step, and get_funnel_sessions lists the sessions that dropped at the worst one.

Check whether yesterday's release broke something. discover_groups scans for frustration signals such as errors and rage clicks and can compare with the previous period to surface regressions, then get_opportunity_stats sizes the one that matters.

Let Claude watch the replay for you. get_session_events fetches a session's full event transcript, and session_screenshot shows what the user saw at a given moment.

What it cannot do: Fullstory's limits page rules out dashboards, heatmaps, privacy rules, user management, billing and settings. Tables stop at 50 rows and session lists at 50 sessions, so it is not an export tool. Nothing runs on its own either: no alert fires when a metric dips overnight. That kind of watch belongs to an automation tool, a different job gathered on our Integrations page. To turn findings into tickets in the same chat, the Claude asana connector can sit next to this one.

Vocabulary

The vocabulary in one minute

Five words you will meet while connecting Fullstory.

Connector
The link you set up once between Claude and an account you already own, so Claude can work in it while it answers you.
Tool
One named thing a connector lets Claude do. Claude picks the tools it needs on its own; the directory lists them by name.
Authorization
The service's own sign-in screen, where you grant the access Claude will use afterwards. Given once per person and revocable.
Approval
The confirmation Claude waits for before doing something that changes your account, shown in the chat at the moment it matters.
MCP
The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Fullstory.
Connect

Plug Fullstory into Claude in three steps

  1. 01

    Find Fullstory in Claude

    In Claude's settings, open Customize, then Connectors, and find Fullstory in the list. On a Team or Enterprise workspace, an Owner or Primary Owner must enable the connector first; each member then signs in individually.

  2. 02

    Start the connection

    Click Connect on its row, then sign in to Fullstory in the window that Fullstory opens itself. If the link ever breaks, use Disconnect and connect again.

  3. 03

    Read the authorization screen

    Read Fullstory's authorization screen before you accept. It belongs to Fullstory, not to Claude, and it decides what the access covers. Then ask Claude which Fullstory tools it can see to confirm.

Tools

The 29 tools, sorted by what they do

Fullstory gives Claude 29 tools: 21 that read your account, 8 that change something in it.

Twenty-one tools read or inspect, eight save definitions in your Fullstory account. Names stay in English, exactly as Claude shows them.

  • 21 read
  • 8 write

What Claude reads (21)

21 tools

Twenty-one tools that compute, look up or replay without touching your saved objects.

compute_funnel

Runs a saved funnel and returns the count at each step, the conversion from the previous step and the conversion from the first one.

When it helps
you want to know whether signup completion improved since the new form went live.

Sourcedeveloper.fullstory.com · September 30, 2026 ↗

compute_journey

Executes a journey and gives its step-by-step breakdown around the pivot event, showing the events users reached at each step outward and the most common end-to-end paths.

When it helps
marketing asks what visitors do right after landing on the pricing page.

Sourcedeveloper.fullstory.com · September 30, 2026 ↗

compute_metric

Executes a metric definition against your data, optionally scoped to a segment and a time range, and returns a count, a table or a trend with a link to Fullstory.

When it helps
you need weekly error counts on the payment page for the incident review.
Watch out
breakdowns stop at 50 rows.

Sourcedeveloper.fullstory.com · September 30, 2026 ↗

discover_groups

Surfaces the leading frustration signals across your product, querying the whole org when no scope is set, and can compare with a prior period to reveal regressions.

When it helps
the morning after a release, you want to see whether anything new is hurting users.

Sourcedeveloper.fullstory.com · September 30, 2026 ↗

discover_org_context

Searches the objects your org has configured, such as pages, named elements, defined and custom events and custom variables, so Claude resolves the right IDs before building anything.

When it helps
you say "the promo banner" and Claude needs to know which element that is.

Sourcedeveloper.fullstory.com · September 30, 2026 ↗

get_funnel

Retrieves saved funnels by ID or by name pattern, with their step count and a readable description, and can be limited to the funnels you own.

When it helps
a colleague mentioned "the onboarding funnel" and you want Claude to reuse it rather than rebuild it.

Sourcedeveloper.fullstory.com · September 30, 2026 ↗

get_funnel_sessions

Lists sessions for one step of a funnel, either the people who completed it or those who dropped off there, each with a direct replay link.

When it helps
step three loses half the traffic and you want to see real examples of it happening.

Sourcedeveloper.fullstory.com · September 30, 2026 ↗

get_journey

Retrieves saved journeys by ID or name pattern, each with a plain-English description of its direction, pivot step, audience and time window, and can be limited to the ones you own.

When it helps
you want to rerun last month's post-checkout journey on this month's data.

Sourcedeveloper.fullstory.com · September 30, 2026 ↗

get_metric

Looks up one or more saved metrics by ID or name pattern and returns their names with a readable description of each definition.

When it helps
before building a new metric, Claude checks whether the team already has one for cart abandonment.

Sourcedeveloper.fullstory.com · September 30, 2026 ↗

get_opportunity_stats

Computes live statistics for one frustration signal: how many users it affects, which pages, domains and devices, and how fast it is growing or shrinking.

When it helps
you need to decide whether a rage-click spike deserves a hotfix today.

Sourcedeveloper.fullstory.com · September 30, 2026 ↗

get_segment

Retrieves one or more saved segments by ID or name pattern, with a human-readable description of who falls into each.

When it helps
someone asks what exactly "power users" means in your Fullstory before you quote a number about them.

Sourcedeveloper.fullstory.com · September 30, 2026 ↗

get_session_events

Fetches a complete, chronological record of everything in a session: clicks, navigations, errors, network requests and more, which Claude can read end to end.

When it helps
a customer reports a failed payment and you want the sequence without watching the recording.

Sourcedeveloper.fullstory.com · September 30, 2026 ↗

get_sessions

Returns sessions that match a metric or a segment, each with a direct replay link, turning an aggregate into concrete user evidence.

When it helps
a metric says mobile errors doubled and you want to see who hit them.
Watch out
it returns 10 sessions by default and 50 at most.

Sourcedeveloper.fullstory.com · September 30, 2026 ↗

get_sessions_for_opportunity

Pulls real sessions where a specific frustration signal was observed, so Claude can read what those users were trying to do at the time.

When it helps
dead clicks cluster on a settings page and support wants three concrete cases.

Sourcedeveloper.fullstory.com · September 30, 2026 ↗

get_view_counts

Counts how often saved segments or metrics were viewed, for up to 10 items of one kind, over a lookback of 30 days by default and 90 at most.

When it helps
you are cleaning up and want to know which metrics nobody opens.

Sourcedeveloper.fullstory.com · September 30, 2026 ↗

session_close

Ends a visual inspection session and frees what it held on Fullstory's side. Fullstory marks it as required after every opened replay, or further openings may be blocked.

When it helps
Claude has finished examining one session and is about to open the next.

Sourcedeveloper.fullstory.com · September 30, 2026 ↗

session_diff

Compares the page structure of an open session between two timestamps and returns a text summary of the differences.

When it helps
a button vanished at some point and you want to know exactly when the page stopped showing it.

Sourcedeveloper.fullstory.com · September 30, 2026 ↗

session_get_a11y_tree

Returns the accessibility tree of an open session at a given page and timestamp, with roles, labels and hierarchy, so Claude can tell which element was actually clicked.

When it helps
an accessibility review needs to confirm a form field had a proper label.

Sourcedeveloper.fullstory.com · September 30, 2026 ↗

session_open

Opens a Fullstory session for visual inspection from the IDs in its replay URL and returns event summaries that help pick the interesting moments.

When it helps
you paste a session link from a bug report and ask Claude to investigate.
Watch out
each opened session must be closed afterwards.

Sourcedeveloper.fullstory.com · September 30, 2026 ↗

session_screenshot

Renders what the user saw in an open session at a given page and timestamp, which is how Claude sees the exact moment you care about.

When it helps
you want to see the exact error message a customer faced before calling them back.

Sourcedeveloper.fullstory.com · September 30, 2026 ↗

session_view

Fullstory lists this tool as deprecated: it no longer works and only returns a message pointing to the screenshot and page-structure tools that replaced it.

When it helps
it does not any more; Claude should go straight to its replacements.

Sourcedeveloper.fullstory.com · September 30, 2026 ↗

What Claude saves (8)

8 tools

Eight tools that save segments, metrics, funnels or journeys in Fullstory. No source gives them their own confirmation: the general rule below applies.

build_funnel

Approval: see the rule

Turns a plain description of ordered user actions into a funnel and saves it in Fullstory, with a link to open it there. It also returns the new funnel's ID.

What Claude asks for
no source describes a confirmation specific to this tool; the general approval rule applies.
When it helps
you want the trial-to-paid path measured the same way by everyone.

Sourcedeveloper.fullstory.com · September 30, 2026 ↗

build_journey

Approval: see the rule

Converts a description of an anchor event and a direction into a journey and saves it, returning a link to Fullstory.

What Claude asks for
nothing tool-specific is documented, so the default rule covers it.
When it helps
you ask what users do before they contact support and want to keep that view.

Sourcedeveloper.fullstory.com · September 30, 2026 ↗

build_metric

Approval: see the rule

Converts a question into a metric definition, as a single number, a top list or a trend. Fullstory's directory sheet says Claude creates the metric in Fullstory so the team can reuse it.

What Claude asks for
no dedicated confirmation is documented; the general rule applies.
When it helps
leadership wants one agreed definition of weekly active users.

Sourcedeveloper.fullstory.com · September 30, 2026 ↗

build_segment

Approval: see the rule

Turns a description of users or behaviour into a Fullstory segment, saves it and returns its ID with a link.

What Claude asks for
no source gives this tool its own confirmation; the general approval rule applies.
When it helps
you want "first-time visitors from paid search" available to the whole team.

Sourcedeveloper.fullstory.com · September 30, 2026 ↗

update_funnel

Approval: see the rule

Adjusts a saved funnel's time window, aggregation, steps or conversion window and saves the result under a new ID, leaving the original funnel as it was.

What Claude asks for
nothing specific is documented; the default rule covers it.
When it helps
the funnel should allow a day to convert, not an hour.

Sourcedeveloper.fullstory.com · September 30, 2026 ↗

update_journey

Approval: see the rule

Modifies a saved journey's time window, direction, attached segment or diagram settings, and saves a new version while the source stays unchanged.

What Claude asks for
no source describes a confirmation for it; the general rule applies.
When it helps
you want the same journey restricted to mobile users.

Sourcedeveloper.fullstory.com · September 30, 2026 ↗

update_metric

Approval: see the rule

Edits an existing metric definition from a plain instruction, such as counting unique users instead of events, and returns a new metric ID.

What Claude asks for
no dedicated confirmation is documented; the default rule applies.
When it helps
a filter for mobile devices is missing.
Watch out
ratio metrics are not supported.

Sourcedeveloper.fullstory.com · September 30, 2026 ↗

update_segment

Approval: see the rule

Updates a saved segment from a plain instruction, for example adding iOS users only or removing a checkout filter, and saves it under a new segment ID.

What Claude asks for
no source describes a specific confirmation; the general approval rule covers it.
When it helps
the cohort needs to exclude internal staff.

Sourcedeveloper.fullstory.com · September 30, 2026 ↗

Approvals

What Claude asks before acting

By default, Claude stops and asks for your confirmation before every action it takes on an account on your behalf. Here that concerns eight tools, the ones that save segments, metrics, funnels and journeys in your Fullstory.

On Team and Enterprise, workspace owners decide whether members may let some actions through without a prompt, and they can restrict what a connector does for the whole organisation, for example keeping reads and closing writes. Nobody overrides that from their own account. Claude works with your Fullstory access and nothing beyond it, and each connection covers a single Fullstory org, never several at once.

Plans

Which plans include it

Of the 819 sheets in the official directory, none shows availability by plan. The connector-by-connector answer is published nowhere, a genuine gap in the catalogue.

The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner switches the connector on for the organisation before members can connect. On the Fullstory side, StoryAI and the protocol toggle must both be enabled for your org. The connector's sheet in the official directory shows its current state.

Limits

Where this connector stops

A connector is not an automation. Claude calls these tools while it answers you: nothing runs by itself when a metric drops or a new error appears.

The eight saving tools are what the sheet exposes today, and an admin can open more actions than any public sheet lists. The directory's partner badge is not a security audit, and Anthropic says on every sheet that it does not choose a publisher's tools. Everything here comes from Fullstory's developer documentation, still marked beta; neither Claude's help centre nor Anthropic's developer docs cover this connector. And two Fullstory pages do not describe writing the same way, as shown below.

Two official sources disagree

Can the Fullstory connector write to your account?

What this page followsBoth pages come from Fullstory and neither carries a date, so neither is out of date on paper. Read together, the tool list is the more precise one: Claude does save segments, metrics, funnels and journeys, but it does not create dashboards, touch privacy rules or manage users. The blanket "no writes" heading is simply too broad.

Need help

Need help connecting Fullstory to Claude?

A person reads every message.

FAQ

FAQ about the Claude Fullstory connector

01What can Claude do with the Fullstory connector?
Claude can answer product questions from your Fullstory behavioural data and back them with real sessions. Its tools define and compute segments, metrics, funnels and journeys, surface and size frustration signals, list the sessions behind a number, and inspect a replay through transcripts, screenshots and page structure. In practice you ask where checkout is leaking or whether a release broke something, and Claude builds the analysis, computes it and links you to the sessions that explain it.
02Can Claude save or change things in Fullstory?
Yes, within a narrow scope. Eight tools save segments, metrics, funnels and journeys in Fullstory, or refine existing ones under a new ID; for funnels and journeys, Fullstory says the original stays unchanged. Beyond that, Fullstory's limits page rules out dashboards, privacy rules, user management, billing and settings. That page is headed as if no writing were possible at all, which the tool list contradicts; the limits section above sets the two pages side by side.
03Does Claude ask before it saves a segment or a metric?
By default, yes: Claude stops and asks for confirmation before each action it takes on an account on your behalf. No source describes a confirmation specific to any Fullstory tool, so that default rule is what covers the eight saving tools. On Team and Enterprise, workspace owners decide which actions members may let through without a prompt, and they can close every saving tool for the organisation , leaving the reading ones open.
04Which Claude plans is the Fullstory connector available on?
No official source publishes plan availability connector by connector, and no directory sheet displays it. Anthropic's general rule is that remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, with an Owner or Primary Owner switching them on first on Team and Enterprise. On the Fullstory side, an org admin must enable StoryAI and the protocol toggle. The Fullstory sheet in the official directory is the only place showing the current state for your account.
05Does Claude see all of our Fullstory data?
Claude sees what your Fullstory access allows, and only within one org per connection: Fullstory says each connection is scoped to a single org and cross-org questions are not supported, so a company with several orgs needs one connection each. Results are also capped, at 50 rows for grouped tables and 50 sessions per list. On the Claude side, a Team or Enterprise owner can restrict what the connector does for the whole organisation, and members cannot lift that setting from their own account.
06Why does Claude say Fullstory is connected but has no tools?
Because StoryAI is probably switched off for your org. Fullstory explains that if StoryAI is opted out, the sign-in completes and the connector shows as connected, yet no tools are available. An org admin has to turn on both StoryAI and the Model Context Protocol toggle in Fullstory's settings. If you cannot see that settings page, you do not have the role needed to change it, and you will need to ask an admin.
07Claude or an automation tool for Fullstory?
They do different jobs, so choose by use. Claude with this connector is for investigations you run in a conversation: define a cohort, compute a metric, read the sessions, explain the cause. It never acts on its own, so it will not watch a metric overnight or post a weekly report by itself. Routines that must run on a schedule or react to an event belong to an automation platform, a different kind of tool rather than a better one.