Limits & What's Not Supported Yet

Fullstory MCP is in private beta and must be enabled for your Fullstory account before you can connect. If you're interested in being one of the first to try Fullstory MCP, sign up for the waitlist here.

What can't the MCP do?

The MCP is in beta and has the following limitations:

• Write operations not supported: You cannot create dashboards, modify privacy rules, or manage users through the MCP.
• No Fullstory account administration: No user management, billing, or settings changes.
• Subset of product features: Not all Fullstory product features are availabile in MCP. The current focus is on metrics, segments, and session replay. Features like dashboards and heatmaps don't currently have MCP support.
• Multi-org / Umbrella accounts: Each MCP server instance is scoped to a single Fullstory org. Auth tokens and API keys are org-level; cross-org querying is not supported. If you manage multiple orgs, you need a separate server connection for each.
• Dimensionality limits: Dimensionality queries (or group by) are limited to 50, which means tables will be capped at 50 rows. This makes the MCP unsuitable for bulk data exports such as large user ID lists.
• Number of sessions: Tools that get sessions default to 10 and have a hard limit of 50 sessions.

We are expanding capabilities with each release. If something you need is missing, submit your feedback to the Slack community.