Fullstory
by Fullstory
Query Fullstory product analytics and read session replays from an AI agent. Fullstory documents 26 tools; Anthropic's directory lists 25. Eleven OAuth scopes, every one read-only — including replay playback.
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.
Connect Fullstory via MCP
https://api.fullstory.com/mcp/fullstoryWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Fullstory Tools & Capabilities (26)
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_segmentandbuild_funnelas 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_closeis documented as required; Fullstory states open sessions hold server-side resources and failing to close them may block furthersession_opencalls. - The Opportunity Lookup tools need a paid tier. Fullstory marks
get_opportunities,get_opportunityandget_sessions_for_opportunityas 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
readOnlyHintvalue is published here. - Two Fullstory sources disagree on
session_open's parameters. The tools reference saysdevice_idandsession_id; Fullstory's own session-review skill passes asession_url. Both may be accepted; we could not check.
Frequently asked questions
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.
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.
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.
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.
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.
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.
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.
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
- Fullstory MCP tools reference (retrieved 2026-08-22) · retrieved 2026-08-22
- Fullstory MCP introduction and prerequisites (retrieved 2026-08-22) · retrieved 2026-08-22
- Fullstory MCP authentication (retrieved 2026-08-22) · retrieved 2026-08-22
- Fullstory MCP FAQ and troubleshooting (retrieved 2026-08-22) · retrieved 2026-08-22
- Fullstory MCP limits (retrieved 2026-08-22) · retrieved 2026-08-22
- Fullstory MCP workflow, visual session investigation (retrieved 2026-08-22) · retrieved 2026-08-22
- Fullstory MCP workflow, build and refine a metric (retrieved 2026-08-22) · retrieved 2026-08-22
- Fullstory MCP workflow, session replay drill-down (retrieved 2026-08-22) · retrieved 2026-08-22
- Fullstory skills and plugin repository (retrieved 2026-08-22) · retrieved 2026-08-22
- Fullstory for Customer Agents MCP integration, the separate
/mcp/activationsserver (retrieved 2026-08-22) · retrieved 2026-08-22 - Fullstory Element Block Rules API (retrieved 2026-08-22) · retrieved 2026-08-22
- Fullstory MCP product page (retrieved 2026-08-22) · retrieved 2026-08-22
- Live OAuth posture check: anonymous handshake returned 401 with a
www-authenticatechallenge naming eleven scopes, RFC 9728 metadata athttps://api.fullstory.com/.well-known/oauth-protected-resource/mcp/fullstory, and authorization server metadata athttps://auth.fullstory.com/.well-known/oauth-authorization-server(2026-08-22) · retrieved 2026-08-22 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- Fullstory support — <mailto:support@fullstory.com> · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Analytics
- Developer
- Fullstory
- Tools
- 26
- Domain
- api.fullstory.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.