--- title: Fullstory remote MCP connector slug: agent-platform/docs/fullstory-remote-mcp-connector docTags: createdAt: 2026-09-23T00:00:00.000Z --- :::hint{type="success"} **Beta** The Fullstory remote MCP connector tools are in beta. ::: The Fullstory remote Model Context Protocol (MCP) connector in Agent Platform brings Fullstory behavioral analytics and session data into Mark. Use [Mark chat](docId\:dtNBEttEGVvkhNkwNypLM), [agents](docId\:w7MSVijPnuFqu4nXDo_bq), and [workflows](docId:2HD0fUsIsfdek516VtN9l) to surface frustration signals, build funnels and journeys, and pull real session replays, all from natural-language questions about your product experience. :::hint{type="info"} **Note** The Fullstory remote MCP is managed by Fullstory. See the [Fullstory MCP introduction](https://developer.fullstory.com/mcp) in the Fullstory Developer Guide for available tools and data. ::: First, a Fullstory account admin must enable Fullstory MCP for your organization, and then a [Mark administrator](docId\:pe0pbUJveWrG8ewvZWDRE) must [connect the Fullstory remote MCP to Mark](docId:4ogM07oy-6RNjj9GZbEzL). After adding the MCP server, individual Mark [users](docId\:L0Ntt9JQmG6fQIJK_Y7C7) and [agent builders](docId\:HOJ_6dibwNf8Qz7WMIDie) log in to Fullstory to access their data from Mark. Administrators only need to add the Fullstory remote MCP once. ## Use cases 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. ### Prioritize testing and experimentation **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. ### Diagnose funnel and journey drop-off **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. ### Audit page quality and experience **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. ### Monitor releases and regressions **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. ## Prerequisites 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: 1. Go to **Settings > Account Management > StoryAI Features**. 2. Toggle **StoryAI** on. 3. Toggle **Model Context Protocol (MCP)** on. 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. ## Connect the Fullstory remote MCP to Mark 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. ### Add Fullstory connection As a Mark administrator, complete the following steps: 1. Go to **Connectors** in Mark. 2. (Optional) Enter *Fullstory* in the search bar to filter the connectors list. 3. Click **Connect** on the **Fullstory** tile. ::Image[]{src="https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/-tiNrVQJcTym7MgLi7U7n_connect-fullstory-mcp.png" size="100" isUploading="false" position="center" width="961" height="690" darkWidth="961" darkHeight="690" showCaption="false" indent="1"} 4. Choose your Fullstory account. ::Image[]{src="https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/e79ioHPNSTRLzUW5lNYUf_fullstory-account.png" size="100" isUploading="false" position="center" width="1234" height="1028" darkWidth="1234" darkHeight="1028" showCaption="false" indent="1"} 5. Log in to Fullstory. 6. Grant the requested permissions and click **Approve**. ::Image[]{src="https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/T1l-FvKyUrSQQrXswbbXK_fullstory-permissions.png" size="100" isUploading="false" position="center" width="1092" height="1562" darkWidth="1092" darkHeight="1562" showCaption="false" indent="1"} A confirmation message displays, and you can close the pop-up window. ### Configure Mark tools After [adding the Fullstory connection](docId:4ogM07oy-6RNjj9GZbEzL), Mark prompts you to select which tools to enable and optionally customize their display names. As a Mark administrator, complete the following steps: 1. Deselect any tools you do not want to add to Mark. 2. (Optional) Update any tool's display name. ::Image[]{src="https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/tSslpvriaGDSRjnwt2V7z_fullstory-tools.png" size="100" isUploading="false" position="center" width="982" height="524" darkWidth="982" darkHeight="524" showCaption="false" indent="1"} 3. Click **Finish**. 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](docId:4ogM07oy-6RNjj9GZbEzL). ## Authenticate with Fullstory 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](docId:4ogM07oy-6RNjj9GZbEzL). 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: 1. Go to **Connectors**. 2. (Optional) Enter *Fullstory* in the search bar to filter the connectors list. 3. Click **Connect** on the **Fullstory** tile. 4. Log in to Fullstory. After you log in to Fullstory, the Fullstory connector tools are available in [Mark chat](docId\:dtNBEttEGVvkhNkwNypLM), [agents](docId\:w7MSVijPnuFqu4nXDo_bq), and [workflows](docId:2HD0fUsIsfdek516VtN9l). ## Fullstory connector tools The Fullstory connector tools are available after an administrator [adds the Fullstory remote MCP to Mark](docId:4ogM07oy-6RNjj9GZbEzL) and you [authenticate with Fullstory](docId:4ogM07oy-6RNjj9GZbEzL). The available tools depend on which tools your administrator enabled. For the full list of tools, parameters, and return values, see the [Tools Reference](https://developer.fullstory.com/mcp) in the Fullstory Developer Guide. The Fullstory connector tools are grouped into the following categories: - **Analytics** – Build and compute custom segments and metrics from a natural language description. - **Funnels** – Build an ordered, multi-step funnel, compute conversion at each step, and pull the sessions behind any step. - **Journeys** – Anchor on a single event and see the paths users took before or after it. - **Sessions** – Pull the sessions behind a metric or segment, and read a session's complete event transcript. - **Agentic session review** – Inspect an open session visually, including a rendered screenshot and accessibility tree, and diff two moments in a session. - **Pages** – Look up existing page definitions to scope other tools to a specific area of your product. - **StoryAI Opportunities** – Discover frustration signals, errors, and regressions across your product, or look up pre-ranked results from Fullstory's ongoing monitoring. Opportunity lookup tools require the StoryAI Premium SKU. ## Update tools To rename, add, or remove tools, a Mark administrator must delete the Fullstory tools registry and re-add it. Complete the following steps: 1. Follow the steps in [Delete a tool registry](docId\:SXjD3qqg-0gS2g4KajfyO). 2. [Add Fullstory connection](docId:4ogM07oy-6RNjj9GZbEzL). 3. [Configure Mark tools](docId:4ogM07oy-6RNjj9GZbEzL). :::hint{type="info"} **Note** If you use Opti ID, administrators can turn off generative AI in the Opti ID Admin Center. See [Turn generative AI off across Optimizely applications](docId\:X5U0kKD2azV5cIdNqwGNj). :::