FAQ & Troubleshooting
Common questions and solutions for the Fullstory MCP server.
Getting started
I added the server but my client can't connect. What should I check?
Confirm the server URL is exactly https://api.fullstory.com/mcp/fullstory with no trailing slash or typo. If everything looks correct, restart your AI client — most clients only load MCP server configurations on startup. If you haven't completed the OAuth authorization flow yet, look for a browser prompt from your client. See the Authentication page for full configuration examples.
Which AI clients are supported?
The Fullstory MCP server works with any client that supports the Model Context Protocol. This includes Claude Desktop, Cursor, VS Code with Copilot, and others. See our client setup guides for configuration instructions specific to each client.
Data & privacy
Does Fullstory MCP respect my fine-grained access control (FGAC) setup?
No. Orgs that require FGAC will not be admitted into the Early Access, as this will be supported in a later version.
Does the MCP respect my Fullstory privacy rules?
Yes. Your existing masking settings, exclusion rules, and element blocking all carry over. The MCP server operates with the same privacy enforcement as the Fullstory UI and API: it does not bypass any rules configured in your account.
Usage
Can I save segments or metrics I create through the MCP?
To protect your configuration during Early Access, you cannot programmatically save segments or metrics. Instead, if a segment or metric is created during your session, the compute_metric tool returns a link to the unsaved object in the Fullstory Analytics app for a user to manually save. If the segment or metric is not saved during the MCP session, it will be discarded once your session ends.
Are there rate limits?
Rate limits will apply during the beta period. If you encounter throttling or receive rate-limit errors, space out your requests or reduce the scope of your queries (narrower time range, more specific segment). If you are consistently hitting rate limits, reach out via the Slack community.
Can I run recurring queries automatically?
The MCP server is a query interface: it responds to requests but does not schedule them. Automation depends on your AI client. Some clients support scheduled prompts, scripted workflows, or integration with automation tools like cron jobs or CI pipelines. As a reminder, all queries are subject to rate limits.
Early Access
How do I get Early Access to Fullstory MCP Beta?
Fullstory MCP Beta access is available to existing paid customers. To sign up for access, fill out the form here.
What are the Support SLAs for Fullstory MCP Beta?
Fullstory MCP Beta is part of our Early Access program and is not covered by Fullstory's standard Support SLAs. Early Access features are opt‑in: customers can use them before general release in exchange for sharing feedback with the product team. Once a feature reaches general availability (GA), it becomes covered under Fullstory's standard Support SLAs.
What is the best way to provide feedback to the Product team?
Fullstory's product team is hosting an external Slack channel to gather feedback and foster collaboration amongst fellow Early Access customers. If a colleague is part of this Slack channel, they may provide your email address to the channel to get you added. If you do not know a colleague in this Slack channel, sign up for the waitlist here and once we confirm your company is part of Early Access, we will add your email to the Slack community.