# FullStory MCP for AI Agents AI Agent Connect > FullStory MCP for AI agents. Manage digital experience intelligence, track user behavior, and pull session recordings directly through your AI client. It connects your FullStory account to your agent so you can query audience segments, fetch specific user profiles, and handle privacy requests without leaving your workspace. ## Overview - **Category:** customer-support - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_JUUCyNnUSrqZlTvYnLFVd8WQHuMjFZOwjQQP8NY8/ai-agent-connect - **Tags:** digital-experience, session-replay, product-analytics, user-behavior, event-tracking, session-metadata ## Description FullStory lets you manage your digital experience intelligence and product analytics through a conversational interface. You can stop jumping between tabs to find that one specific user who hit a wall during checkout. Instead of digging through a dashboard, you just ask your AI agent to pull up the last three sessions for a specific ID. It handles the heavy lifting of filtering through telemetry to show you exactly where the friction happened. If you need to see how a certain group is interacting with a new feature, you can ask the agent to pull up your audience segments and summarize the behavior. It also handles the boring stuff like logging custom backend events or making sure you're following privacy rules by deleting user data on command. By connecting this to your workflow via the Vinkius catalog, you turn your analytics into a conversational interface where you actually get answers instead of just staring at charts. Product managers and support engineers can use this to understand why users drop off or replicate bugs. You can verify workspace stats, check raw data bundles for deeper analysis, and maintain an accurate identity map of your subscribers. It removes the friction of manual data entry and lets you focus on fixing the problems you see in the data. ## Tools ### get_session Get deep metadata and playback links for a specific session recording. This helps you see exactly how a user navigated your site. ### get_user Pull a full tracking profile including custom variables and behavior history for a user. It gives you a complete view of a subscriber's journey. ### list_exports Check the status and download links for your bulk data export jobs. You can monitor these offloads for warehouse ingestion. ### delete_user Permanently erase a user profile and all associated session history for privacy compliance. This is essential for handling GDPR and CCPA requests. ### get_account_info Verify your integration is active and see your basic platform stats. Use this to check your workspace scope and connection health. ### get_session_events Fetch the chronological list of clicks, navigation changes, and error logs for a session. It exposes the precise structural DOM changes. ### list_segments See your saved audience definitions and the number of users in each segment. This helps you understand high-level audience behavior. ### list_sessions Search for and list session recordings based on specific telemetry criteria. You can find specific playback links quickly. ### list_users Query the subscriber directory to see aggregate behavioral profiles and custom parameters. It helps you map out your user base. ### create_event Send a custom backend event into FullStory to enrich your data with server-side metrics. This is useful for tracking events that bypass the frontend. ### create_update_user Sync custom tenant data into FullStory to give your sessions more context. Use this to maintain accurate identity mapping. ## Prompt Examples **Prompt:** ``` Find the last 5 sessions for user 'user_99' and tell me if they saw any errors. ``` **Response:** ``` I've pulled the latest activity for user_99. Here are the last 5 sessions: | Date | Session ID | Status | | :--- | :--- | :--- | | Oct 12 | sess_882 | **Error Found** | | Oct 11 | sess_871 | Success | | Oct 10 | sess_860 | Success | | Oct 09 | sess_844 | **Error Found** | | Oct 08 | sess_832 | Success | In the sessions from Oct 12 and Oct 09, the user encountered a '404 Page Not Found' error during the checkout flow. ``` **Prompt:** ``` Who is in our 'High Value' segment and what's their common behavior? ``` **Response:** ``` The **High Value** segment currently contains **1,452 users**. Based on their recent telemetry, here is their common behavior: * **High Frequency:** They visit the dashboard an average of 4 times per day. * **Core Action:** 85% of their interactions occur within the 'Analytics' tab. * **Navigation:** They primarily use the 'Export' and 'Filter' buttons more than the average user. ``` **Prompt:** ``` I need to delete the data for customer 'john_doe@example.com' for a GDPR request. ``` **Response:** ``` I have successfully processed that request. The user profile for **john_doe@example.com** has been permanently erased from FullStory, including all associated session history and custom property links. ``` ## Capabilities ### Pull specific session recordings Get playback links and metadata for a user's journey to see exactly where they struggled. ### Fetch detailed user profiles See custom variables and behavior history for any subscriber in your analytics boundary. ### Query audience segments List your saved filters and see how many people are in each dynamic audience group. ### Log backend events Send custom data from your server directly into FullStory to enrich your datasets. ### Handle privacy deletions Remove user profiles and telemetry to stay compliant with GDPR and CCPA requests. ### Monitor data exports Check the status of your bulk data offloads and get download links for warehouse ingestion. ### View session telemetry See the exact sequence of clicks, navigation changes, and error logs for any session. ## Use Cases ### Debugging a checkout error A support lead asks the agent to find the last 5 sessions for a specific user and look for error logs using get_session_events. ### Analyzing a new feature A product manager asks the agent to list the High Value segment and summarize the behavior of people in that group. ### Automating GDPR requests A privacy officer tells the agent to delete a specific user profile using delete_user to clear the compliance queue. ### Tracking backend success An engineer uses create_event to log a successful subscription renewal that happened on the server. ## Benefits - Stop manual dashboard hunting by using list_sessions to find specific recordings in seconds. - Speed up troubleshooting with get_session_events to see the exact click trail leading to an error. - Simplify privacy compliance by using delete_user to handle data erasure requests instantly. - Enrich your data with create_event to capture backend metrics that JavaScript can't see. - Get instant audience insights by using list_segments to see how many users fall into your filters. - Keep your data synced with create_update_user to ensure your AI has the latest user context. ## How It Works The bottom line is you get a conversational way to query your entire digital experience dataset without opening the FullStory dashboard. 1. Subscribe to the FullStory MCP on Vinkius and grab your API key from the FullStory settings. 2. Paste that key into your AI client to establish the connection. 3. Ask your agent to find a user, summarize a session, or pull a segment. ## Frequently Asked Questions **Can the FullStory MCP find specific user recordings?** Yes, it can pull session links and metadata for specific users or based on telemetry filters, allowing you to see exactly how a user navigated your site. **How does the FullStory MCP help with privacy compliance?** You can use it to permanently delete user profiles and their history to satisfy GDPR or CCPA requests via simple AI commands. **Can I use the FullStory MCP to track backend events?** Yes, it lets your agent send custom events from your server directly into your FullStory dataset, which is perfect for tracking actions that bypass the frontend. **Does the FullStory MCP show me audience segments?** It can list your saved audience definitions and tell you how many users are in each segment, helping you understand high-level audience behavior. **Can I get a list of all users in FullStory?** Yes, the Connector can query your subscriber directory to show aggregate behavioral profiles and custom parameters across your analytics boundary. **How do I connect FullStory to my AI agent?** You just need your API key from the FullStory settings to connect the Connector through the Vinkius catalog, then you can start querying your data. **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.