Fullstory remote MCP connector

The Fullstory remote Model Context Protocol (MCP) connector in Mark (Optimizely Agent Platform) brings Fullstory behavioral analytics and session data into Mark. Use Mark chat, agents, and workflows to surface frustration signals, build funnels and journeys, and pull real session replays, all from natural-language questions about your product experience.

First, a Fullstory account admin must enable Fullstory MCP for your organization, and then a Mark administrator must connect the Fullstory remote MCP to Mark. After adding the MCP server, individual Mark users and agent builders log in to Fullstory to access their data from Mark. Administrators only need to add the Fullstory remote MCP once.

The following use cases show how you can use Fullstory connector tools in Mark to turn behavioral data into a prioritized backlog, a root-cause diagnosis, or a regression alert.

Goal – Turn friction signals into a ranked test backlog.

Friction-ranked test backlog – Use discover_groups, scoped to your checkout and cart pages with compare_to_previous enabled, to find the top frustration and error groups over the last 30 days against the prior period. Use get_opportunity_stats and build_metric to turn each finding into a prioritized A/B test backlog with a hypothesis and a primary metric.

Goal – Find where users abandon a flow and see what happened next.

Funnel drop-off by device – Use build_funnel and compute_funnel to build a funnel from product listing, to product detail, to add to cart, to checkout, to confirmation, broken down by device type. Use get_funnel_sessions with did_not_complete=true to pull session replays from the worst-converting step on mobile.

Live experiment journey impact – Use build_segment to define users who visited an experiment page in the last 14 days, then use build_journey and compute_journey to reveal the downstream detour paths a conversion metric alone would miss. Use get_journey_sessions to pull the sessions behind any path.

Goal – Find underperforming pages and diagnose the root cause.

High-traffic, low-quality pages – Use get_pages and build_metric to rank your top pages by traffic and bounce rate over the last 30 days and flag above-median underperformers. Use discover_groups to pull dead-click counts and session_open with session_screenshot to review a session replay for the worst pages, to diagnose whether the problem is content, layout, or a broken interaction.

Goal – Catch site-wide regressions after a release.

Post-release regression sweep – Use discover_groups with compare_to_previous enabled to compare frustration signals and console errors from the last 7 days against the prior 7 days, site-wide. Use get_opportunity_stats to break any regressions down by browser and page, then cross-reference the affected pages against your live experiments to flag which ones to pause or annotate.

Fullstory MCP requires two org-level settings in Fullstory, in addition to connecting Mark. Before a Mark administrator connects Fullstory, a Fullstory account admin must complete the following steps in Fullstory:

If StoryAI is not enabled for your org, the connection between Mark and Fullstory still succeeds, but no tools become available. Confirm both toggles are on before you troubleshoot a connection that displays connected without any tools.

The first person to connect a third-party service to Mark should be an administrator of that service. Administrator access installs the complete set of tools, so Mark adds every available tool. If a non-administrator connects the service first, Mark installs only the tools that account can access.

As a Mark administrator, complete the following steps:

A confirmation message displays, and you can close the pop-up window.

After adding the Fullstory connection, Mark prompts you to select which tools to enable and optionally customize their display names.

As a Mark administrator, complete the following steps:

The Fullstory tile displays Connect on the Connectors tab for Mark users to authenticate with their personal accounts.

To update the available tools or names, see Update tools.

Each Mark user and agent builder logs in to Fullstory individually to access their data from Mark. User-level authentication ensures you access only the data your Fullstory account is authorized to view.

Before you begin, confirm that a Mark administrator has connected the Fullstory remote MCP to Mark. Until an administrator connects it, the Fullstory tile displays Contact admin instead of Connect and you cannot select it.

To authenticate, complete the following steps in Mark:

After you log in to Fullstory, the Fullstory connector tools are available in Mark chat, agents, and workflows.

The Fullstory connector tools are available after an administrator adds the Fullstory remote MCP to Mark and you authenticate with Fullstory. The available tools depend on which tools your administrator enabled. For the full list of tools, parameters, and return values, see the Tools Reference in the Fullstory Developer Guide.

The Fullstory connector tools are grouped into the following categories:

To rename, add, or remove tools, a Mark administrator must delete the Fullstory tools registry and re-add it. Complete the following steps: