# FullStory MCP

> FullStory FullStory MCP lets your AI agent analyze deep user behavior and digital experience intelligence. You can ask it to fetch specific session playbacks, audit user profiles across devices, or track custom events directly from chat. It turns complex analytics tasks—like finding why a checkout flow failed—into simple questions for your agent.

## Overview
- **Category:** customer-support
- **Price:** Free
- **Tags:** digital-experience, session-replay, product-analytics, user-behavior, event-tracking, session-metadata

## Description

Figuring out where users drop off or what features they ignore used to mean jumping between dashboards and manually piecing together timelines. Now, you can connect your FullStory account directly through this MCP. Your AI client handles the heavy lifting of product analytics, letting you query complex data—like tracking a specific click or pulling up a user's full activity history—using natural conversation. It gives you immediate visibility into how people use your site or app.

Whether you need to check a customer’s profile across multiple devices or programmatically log an event that bypassed the front-end code, this MCP handles it all. When you subscribe via Vinkius, your agent gets instant access to FullStory's entire data set of user interactions and session records. You stop building complex custom scripts just to answer basic questions about user journeys.

## Tools

### delete_user
Permanently removes a user's private telemetry, property links, and session history from FullStory.

### get_account_info
Validates the connection by retrieving basic platform statistics and defining the workspace scope.

### get_session_events
Fetches a complete timeline of all captured events, including clicks, navigation changes, and DOM structure alterations for one session.

### get_session
Retrieves core metadata about an entire recording, like total active time, page transitions, and event markers.

### get_user
Gathers a user's full tracking profile, including custom variables and cross-device interaction boundaries.

### list_exports
Lists the status of bulk data export jobs, showing processing states and download URLs for warehouse ingestion.

### list_segments
Retrieves definitions of saved audience groups, including how many members are in those segments over the last 30 days.

### list_sessions
Searches for session recordings by specific criteria and provides links to view them based on their telemetry data.

### list_users
Queries the directory to list user identities, custom parameters, and aggregate behavioral profiles across your site.

### create_event
Sends a custom backend event into FullStory that wasn't captured by the front-end JavaScript client.

### create_update_user
Synchronizes or updates specific user identity data into FullStory to improve context for session tracking.

## Prompt Examples

**Prompt:** 
```
List the last 5 sessions for user UID 'user_12345'.
```

**Response:** 
```
Retrieving sessions... I found 5 recent recording sessions for UID user_12345. Key sessions include a 'Checkout' flow from yesterday and a 'Login' event from this morning. Which playback link would you like?
```

**Prompt:** 
```
Show me the full profile details for FullStory ID '123:456'.
```

**Response:** 
```
Fetching user data... For ID 123:456, I found email 'customer@example.com'. They are part of the 'Premium' segment and have 15 custom properties, including 'total_spent: 150.00'.
```

**Prompt:** 
```
Track a server event 'Subscription Renewed' for user 'johndoe@email.com'.
```

**Response:** 
```
Event tracked! I have successfully posted the 'Subscription Renewed' event to FullStory for johndoe@email.com. This data will now appear in their user timeline.
```

## Capabilities

### Audit User Profiles
Get a full profile history for any specific user, including their total duration on the site and all associated custom variables.

### Search & Retrieve Sessions
List or search multiple session recordings based on criteria like date range or browser type, and retrieve deep metadata for a single recording.

### Analyze Interaction Events
Fetch the entire chronological list of actions—clicks, navigation changes, and custom events—that happened during any recorded session.

### Programmatic Data Logging
Inject custom backend metrics or automatically update user identities into FullStory using simple commands.

### Manage Compliance & Exports
Delete specific user data to meet privacy regulations like GDPR, or list raw data bundles ready for deep analytical processing.

## Use Cases

### A critical checkout flow failed for a premium user.
The support engineer asks the agent: 'What happened during the last 10 minutes of activity for this customer?' The agent uses `get_session_events` and provides a detailed list showing the exact navigation mutation that triggered the error, allowing immediate resolution.

### We suspect our new sign-up flow is confusing users.
The product manager asks the agent to 'List all users who started but didn't finish onboarding.' The agent uses `list_users` and then pulls detailed profiles using `get_user` for a small sample group, showing custom properties like total spent.

### We need to prove GDPR compliance for historical data.
The privacy officer simply instructs the agent: 'Delete all records associated with user Jane Doe.' The agent executes `delete_user`, logging the action and confirming the permanent removal of sensitive telemetry.

### We launched a new feature that needs tracking from our API.
Instead of waiting for front-end changes, the developer asks the agent to 'Track an event called Payment Processed.' The agent runs `create_event`, ensuring the backend data is logged correctly into FullStory immediately.

## Benefits

- Pinpoint user failure points. Instead of guessing, you can use the agent to fetch the complete set of captured events for a session ID, showing exactly where clicks or errors occurred.
- Maintain data integrity easily. You don't have to manually update records; just ask your agent to run `create_update_user` to sync custom tenant data into FullStory tracking.
- Understand the customer journey at scale. Use `list_sessions` and `get_session` to search for multiple recordings, providing playback links and metadata overlays without touching a dashboard.
- Ensure compliance automatically. If you need to delete sensitive data quickly, running `delete_user` is one simple command that handles the removal of telemetry and session history.
- Improve data quality from your backend. You can now programmatically log custom interactions using `create_event`, enriching FullStory datasets with server-side metrics.

## How It Works

The bottom line is that your AI client talks directly to FullStory's core data layer without needing manual API calls or complex integrations.

1. Subscribe to this MCP through the Vinkius Marketplace and enter your FullStory API Key.
2. Tell your AI agent what you need, like 'Show me all events for user 123.'
3. The agent executes the request against FullStory and returns the structured data right back in the chat.

## Frequently Asked Questions

**How do I get an API Key for FullStory?**
Log in to FullStory, navigate to Settings > API Keys, and click on 'Create Key' to generate a new token with Admin or Architect permissions.

**What is the difference between ID and UID?**
The 'id' is a system-generated unique identifier from FullStory, while the 'uid' is your application's own internal user ID passed via FS.identify.

**Can I watch session playbacks through the agent?**
The agent can retrieve the 'fsUrl' for any session, which is a direct link to watch the playback in your browser. You cannot watch the video inside the chat interface directly.

**Are custom user properties supported?**
Yes! When you use 'upsert_user' or 'get_user_details', all custom properties stored in the 'properties' object are accessible and manageable via the agent.