Fullstory

Query Fullstory product analytics and read session replays.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Fullstory connector does

The Fullstory MCP server connects your product analytics and session replay archive to Claude, ChatGPT and any MCP-compatible agent. Fullstory documents 26 tools that build metrics and segments, compute funnels, surface frustration signals, and render actual replay frames of what a real user saw. Sign-in is OAuth or an API key. Every advertised scope is read-only.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Fullstory tools (26)

  • build_funnel
  • build_journey
  • build_metric
  • build_segment
  • compute_funnel
  • compute_journey
  • compute_metric
  • discover_groups
  • discover_org_context
  • get_funnel
  • get_funnel_sessions
  • get_journey
  • get_metric
  • get_opportunity_stats
  • get_segment
  • get_session_events
  • get_sessions
  • get_sessions_for_opportunity
  • get_view_counts
  • session_close
  • session_diff
  • session_get_a11y_tree
  • session_open
  • session_screenshot
  • session_view
  • update_funnel
  • update_journey
  • update_metric
  • update_segment

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Fine-grained access control is not honoured. Fullstory states the MCP does not respect FGAC and that orgs requiring it are excluded from Early Access. Per-user data restrictions inside Fullstory do not constrain an MCP-connected agent.
  • Nothing is saved without a human. Metrics, segments and funnels built through the connector are drafts with a link into the Fullstory UI; Fullstory states unsaved objects are discarded when the session ends. Note that Fullstory's tools reference contradicts this by describing build_segment and build_funnel as persisting — the discrepancy is Fullstory's, unresolved.
  • No writes, no administration. No dashboards, no privacy-rule changes, no user management, no billing or settings access. No advertised scope permits any of it.
  • Not all of Fullstory is reachable. Fullstory names dashboards and heatmaps as features with no MCP support; the current focus is metrics, segments and session replay.
  • Result sets are small by design. Session-returning tools default to 10 sessions with a hard cap of 50, and group-by queries cap at 50 rows. Fullstory states this makes the MCP unsuitable for bulk exports such as large user ID lists.
  • One org per connection. Auth tokens and API keys are org-level and cross-org querying is not supported. Multi-org and umbrella accounts need a separate connection each.
  • Rate limited to 3 requests per second with a burst of 20, applied per org and per MCP endpoint, tracked separately from the Server API limits.
  • Session review tools leak resources if misused. session_close is documented as required; Fullstory states open sessions hold server-side resources and failing to close them may block further session_open calls.
  • The Opportunity Lookup tools need a paid tier. Fullstory marks get_opportunities, get_opportunity and get_sessions_for_opportunity as available only to StoryAI Premium SKU customers.
  • Beta, with no support SLA. Fullstory states Early Access features are not covered by its standard support SLAs until general availability.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail or readOnlyHint value is published here.
  • Two Fullstory sources disagree on session_open's parameters. The tools reference says device_id and session_id; Fullstory's own session-review skill passes a session_url. Both may be accepted; we could not check.

Frequently asked questions

Can the Fullstory MCP server watch session replays of real users?

Yes, and this is its defining capability. The agentic session review tools render actual replay frames: session_screenshot returns a rendered image of what one identified end user saw at a timestamp, session_get_a11y_tree returns the page structure with roles and labels, and session_diff reports what changed between two moments. The playback:read scope grants this.

Does the Fullstory connector return personal data about my end users?

It returns whatever your capture configuration already stores, which is not nothing. Screenshots reproduce the rendered page, and get_session_events returns a full chronological transcript of clicks, navigations, errors and network requests for a named device and session. Fullstory states your masking, exclusion and element-blocking rules carry over unchanged, so the MCP inherits your privacy posture rather than adding one.

Can the Fullstory MCP server write anything to my account?

Effectively no, despite six tool names beginning with build or update. All eleven OAuth scopes the server advertised on 2026-08-22 end in read, with no write scope of any kind. Fullstory's own documentation states that write operations are not supported and that a metric or segment built through MCP is a draft you must save yourself in the Fullstory UI.

How many tools does the Fullstory MCP server have?

Fullstory documents 26; Anthropic's directory lists 25, and the two lists are not the same 25. Four documented tools are missing from the directory and three directory names appear in no Fullstory documentation we could reach. One documented tool, session_view, Fullstory marks as deprecated and no longer functional.

Is session replay content safe to feed into an AI agent?

Treat it as untrusted input, always. Replay records what members of the public typed and saw on your site, so a screenshot, accessibility tree or event transcript can carry text an anonymous visitor chose to put there. That makes every session read a prompt-injection surface. Never let retrieved replay content act as instructions to the agent.

Why does the Fullstory MCP server connect but show no tools?

Because StoryAI is switched off for your org. Fullstory states the OAuth handshake still completes successfully when StoryAI is opted out, so your client reports the server as connected while it exposes zero tools. An account admin must enable both the StoryAI toggle and the Model Context Protocol toggle under Settings, then restart the client.

What do I need before connecting Fullstory to Claude?

An admin who has enabled two toggles, and a Fullstory org without fine-grained access control. Fullstory requires both StoryAI features and the Model Context Protocol toggle switched on under Settings, Account Management, StoryAI Features. Fullstory also states orgs that require fine-grained access control are not admitted to the beta, because the MCP server does not yet honour it.

Are there rate limits on the Fullstory MCP server?

Yes, three requests per second with a burst allowance of 20. Fullstory applies that limit per org and per MCP endpoint, and states it is tracked separately from the public Server API limits. Separate caps also apply to results: session-returning tools default to 10 and cap at 50, and group-by queries cap at 50 rows.

Sources

More Analytics connectors

  • Aleph

    Query live FP&A data, build reports and update dashboards from your AI assistant.

  • august

    Interview simulated customer twins, run focus groups and surveys from an AI agent.

  • ChartMogul

    Query MRR, ARR, churn, retention, cohorts, customers and sales pipeline from your AI assistant.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Fullstory to work.

Connect Fullstory once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio