FullStory MCP. Analyze deep digital behavior through conversation.
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.
Give Claude and any AI agent real-world access
Get a full profile history for any specific user, including their total duration on the site and all associated custom variables.
List or search multiple session recordings based on criteria like date range or browser type, and retrieve deep metadata for a single recording.
Fetch the entire chronological list of actions—clicks, navigation changes, and custom events—that happened during any recorded session.
Inject custom backend metrics or automatically update user identities into FullStory using simple commands.
Delete specific user data to meet privacy regulations like GDPR, or list raw data bundles ready for deep analytical processing.
Ask an AI about this
Waiting for input…
What AI agents can do with FullStory MCP: 11 Tools for Analytics
These tools let your AI agent perform specific actions in FullStory. Use them to manage user identity, retrieve sessions, or inject custom events into your analytics data.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using FullStory MCPDelete 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...
Get Session Events
Fetches a complete timeline of all captured events, including clicks, navigation...
Get Session
Retrieves core metadata about an entire recording, like total active time, page...
Get User
Gathers a user's full tracking profile, including custom variables and cross-device...
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...
List Users
Queries the directory to list user identities, custom parameters, and aggregate...
Create Event
Sends a custom backend event into FullStory that wasn't captured by the front-end...
Create Update User
Synchronizes or updates specific user identity data into FullStory to improve...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with FullStory, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by FullStory. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Manually connecting user actions to business problems takes forever.
Right now, figuring out why a feature isn't working involves clicking into the dashboard, filtering by date range, manually selecting different users, and then cross-referencing multiple views just to find one specific error or failed step. It’s slow, tedious work that requires dozens of clicks and copy-pasting.
With this MCP, you simply ask your agent a question—like 'Show me the full activity history for user X'—and it executes the necessary tools like `get_user` and `list_sessions`. You get the structured data instantly in plain text. No manual clicks, no dashboard hopping.
Get complete visibility into a customer’s journey with FullStory.
The process of auditing user activity used to require navigating through multiple tabs and joining datasets manually. You had to fetch the profile data, then separately pull the session metadata, and finally correlate those timestamps yourself.
Now you can ask for a comprehensive overview, letting your agent handle the complexity behind the scenes. It combines `get_user` with `list_sessions` in one conversational turn. The difference is immediate: contextually rich answers instead of isolated data points.
What FullStory MCP does for your AI
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.
019d75a1-c088-7070-99cb-bc8ad93d6476 How to set up FullStory MCP
The bottom line is that your AI client talks directly to FullStory's core data layer without needing manual API calls or complex integrations.
Subscribe to this MCP through the Vinkius Marketplace and enter your FullStory API Key.
Tell your AI agent what you need, like 'Show me all events for user 123.'
The agent executes the request against FullStory and returns the structured data right back in the chat.
Who uses FullStory MCP
This MCP is essential for Product Managers and support teams who are tired of manually cross-referencing dashboards just to answer a basic question about user behavior. If you regularly need context on why a customer failed at checkout, this tool saves hours of clicking.
You use it to quickly check activity or find specific session playbacks to validate hypotheses about product usage patterns.
You get a real-time, detailed overview of a customer's recent interaction events while troubleshooting an issue and speaking directly with the user.
You use it to pull structured data points—like listing segments or checking full profile metadata—to feed into secondary analysis models.
Benefits of connecting FullStory MCP
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.
FullStory MCP 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.
FullStory MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Trying to analyze raw logs manually
A team member tries to find out why a user exited by searching through multiple raw API endpoints and piecing together timestamps from different services.
Just ask your agent. For instance, tell it to list_sessions for the last week, then select a session ID, and finally run get_session_events on that specific recording.
Forgetting to update identity records
The system sees 'User A' logging in from one device but fails to link subsequent actions because the profile was never updated with a new ID.
Before analyzing, run create_update_user to synchronize any custom tenant data. This ensures all sessions are mapped under the correct user identity.
Assuming frontend coverage for server actions
A backend process completes successfully but has no record of that activity in FullStory's timeline, leading to inaccurate analytics.
Use create_event to programmatically inject the necessary metrics. This guarantees the data appears in the user timeline even if front-end JavaScript can't capture it.
When to use FullStory MCP
Use this MCP if your job requires answering specific, deep questions about user behavior (e.g., 'What did they click?' or 'Why did they fail at checkout?'). It excels when you need to pull granular data like get_session_events or manage compliance via delete_user. Don't use it if your goal is general dashboard reporting, which should stay in the main FullStory UI. If you simply need a high-level count of users without context, listing segments (list_segments) works, but for deep troubleshooting, this MCP is unmatched because it lets your agent handle the complex data retrieval flow across multiple tools.
Frequently asked questions about FullStory MCP
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.