FullStory for AI agents

FullStory is a digital experience analytics platform that captures user sessions and events to help teams understand product behavior and diagnose where users struggle. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

AnalyticsAPI keyMCP + RESTfullstory.com
AUDIT LOG · FULLSTORYPOLICY: acme-support
09:41:07 · claude · u_8f2read
fullstory.list_datasets
List Datasets✓ allowed · 212ms
09:41:08 · claude · u_8f2read
fullstory.get_user
Get User✓ allowed · 164ms
09:41:09 · claude · u_8f2write
fullstory.create_annotation
Create Annotation✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
fullstory.delete_user_data
Delete User Data✕ blocked · policy: deny
EVERY FULLSTORY CALL, ON THE RECORD
01 · USE CASES

What agents do in FullStory.

01

Search for a user's sessions

Search users to find the session where a customer hit a specific bug.

02

Check a segment's definition

Get a segment's criteria to confirm which users it currently includes.

03

Confirm before deleting user data

Require approval before deleting user data, since it is often tied to a privacy or compliance request.

02 · ACTIONS

30 FullStory actions, graded by risk.

Every FullStory action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

17

Look things up. Allowed by default.

  • fullstory.get_user
    Get User
  • fullstory.get_account
    Get FullStory Account
  • fullstory.get_segment
    Get Segment
  • fullstory.search_users
    Search Users
  • fullstory.get_operation
    Get Operation
  • fullstory.list_datasets
    List Datasets
  • fullstory.list_segments
    List Segments
  • fullstory.list_sessions
    List Sessions
  • fullstory.list_operations
    List Operations
  • fullstory.get_import_status
    Get Import Status
  • fullstory.get_extraction_rule
    Get Extraction Rule
  • fullstory.list_element_blocks
    List Element Blocks
  • fullstory.list_import_records
    List Import Records
  • fullstory.list_extraction_rules
    List Extraction Rules
  • fullstory.get_recording_settings
    Get Recording Settings
  • fullstory.get_organization_quotas
    Get Organization Quotas
+ 1 MORE

write

7

Create and change things. Allow, or ask the user first.

  • fullstory.create_annotation
    Create Annotation
  • fullstory.create_extraction_rule
    Create Extraction Rule
  • fullstory.update_extraction_rule
    Update Extraction Rule
  • fullstory.upsert_user
    Upsert User
  • fullstory.import_users
    Import Users
  • fullstory.import_events
    Import Events
  • fullstory.set_extraction_rule_archived
    Set Extraction Rule Archived

destructive

6

Delete, cancel or archive. Ask first, or deny outright.

  • fullstory.cancel_operation
    Cancel Operation
  • fullstory.delete_user_data
    Delete User Data
  • fullstory.delete_element_block
    Delete Element Block
  • fullstory.get_element_block
    Get Element Block
  • fullstory.create_element_block
    Create Element Block
  • fullstory.update_element_block
    Update Element Block
03 · HOW IT WORKS

FullStory in three steps.

  1. 01Your users connect FullStoryThey add their FullStory api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “create Annotation” can wait for the user, and “delete User Data” can be denied outright.
  3. 03Any agent can actYour agent calls FullStory through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('fullstory', {
  read: 'allow',
  write: 'ask',        // create_annotation
  destructive: 'deny',  // delete_user_data
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How FullStory connects.

Users add their FullStory api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same FullStory connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use FullStory from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
07 · FAQ

FullStory and Arc0, answered.

Q01

Can I use FullStory with Claude, ChatGPT or Cursor?

Yes. Connect FullStory to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the FullStory actions you allow.

Q02

How do users connect FullStory?

Users add their FullStory api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which FullStory actions can my agent take?

30 in total: 17 read, 7 write and 6 destructive, such as “create Annotation”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in FullStory?

Yes. Actions like “delete User Data” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call FullStory too?

Yes. The same FullStory connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug FullStory into your agent.

Your users connect FullStory once, under your brand. Your agent gets 30 actions behind your policies, with every call on the record.

Free to build · MCP + REST · Audit log on every plan