Skip to content
actionlake
Start free

Connectors · Marketing & media

Fullstory MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Fullstory and the rest of your systems. It gives your agent 68 Fullstory actions (41 reads, 22 writes and 5 that wait for a confirmation) and holds the Fullstory credential itself, so the agent never does. It paces Fullstory's limits and records every call.

Connect Fullstory freeSee pricing

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp
the first call
do {  action: "fullstory.users.list",  intent: "check which Fullstory account is connected"}# List Users · read · 1 upstream call
  • 68actionsin one signed file
  • 41readlook, never change
  • 22writecreate and update
  • 5wait for a yesdestructive, confirmed first

Set up

Connect Fullstory in three steps.

  1. 01

    Add actionlake to Claude.

    Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.

    https://connect.actionlake.com/mcp
  2. 02

    Connect Fullstory.

    API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.

    • api_keyFullstory API key (Settings > Integrations > API Keys
    account { op: "connections.requirements", service: "fullstory" }
# free: exactly what to paste, and what is found for you
  3. 03

    Make the first call. Check before a write.

    Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

    do    { action: "fullstory.users.list" }# list users · read · 1 upstream callcheck { action: "fullstory.users.delete", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Fullstory at a glance

Sign-in
API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.
You provide
api_key
Limits we pace to
300 calls a minute, per connection
API covered
Fullstory Server API v2 (+ v2beta and the v1 endpoints still documented)api.fullstory.com
Built from
Fullstory's documentation, read 23 October 2026developer.fullstory.com
Service file
Version 1.0.0, signed (Ed25519)
Cached reads
35 of 41 reads, for up to an hour; a write clears what it affects
Shared entities
1, so ask can line Fullstory up with your other systems
Data
Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Fullstory.

68 actions in 15 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

  • 41readlook, never change
  • 22writecreate and update
  • 5destructivewait for a confirmation

  1. Users

    15

    7 read · 6 write · 2 destructive

    List Users · Get User · Update User · Delete User

  2. Settings

    13

    12 read · 1 write · 0 destructive

    Get Recording Block Rules History · Get Domain Settings History · Get Recording Features History · Get Geo Settings History

  3. Extraction rules

    7

    2 read · 5 write · 0 destructive

    Create Extraction Rule · List Extraction Rules · Archive Extraction Rule · Get Extraction Rule

  4. Sessions

    6

    4 read · 2 write · 0 destructive

    List Sessions · Generate Context · Get Session Events · Generate Summary With Overrides

  5. Element block rules

    5

    2 read · 2 write · 1 destructive

    Create Element Block Rule · List Element Block Rules · Get Element Block Rule · Update Element Block Rule

  6. Events

    5

    3 read · 2 write · 0 destructive

    Create Event · Create Batch Events Import Job · Get Batch Events Import Errors · Get Batch Events Imports

  7. Summary profiles

    5

    2 read · 2 write · 1 destructive

    Create Profile · List Profiles · Get · Update

  8. Operations

    3

    2 read · 0 write · 1 destructive

    List Operations · Get Operation Status · Cancel Operation

7 more areas · 9 actions
  • Segments 3
  • Annotations 1
  • Datasets 1
  • Exports 1
  • Me 1
  • Organization 1
  • Search exports 1

Top actions

The Fullstory API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 5 of Fullstory's 5 action names are shared with at least one other connector, so an agent learns them once.

ActionWhat it doesEffectSame name in
fullstory.users.listList UsersRetrieve a list of users matching the supplied filter criteriareadcrm.contact.list177 connectors
fullstory.users.getGet UserRetrieve details for a single userreadcrm.contact.get176 connectors
fullstory.users.deleteDelete UserDelete a single user.destructivecrm.contact.delete147 connectors
fullstory.datasets.listList DatasetsReturns the datasets your credentials can read.readthis connector
fullstory.events.createCreate EventCreates one event with the specified details.writethis connector
fullstory.sessions.listList SessionsReturns up to `limit` most recent session replay URLs for a user, queried by `uid` and/or `email`. If both `uid` and `email` are provided, this endpoint…readthis connector
fullstory.annotations.createCreate AnnotationCreates an annotation with the specified details.writethis connector
fullstory.extraction_rules.listList Extraction RulesLists extraction rules for the organization. Filters by scope (required), optional property name and archive status. Returns all matching rules (no request…readthis connector
fullstory.summary_profiles.listList ProfilesReturns a list of summarization Profiles which specifies both prompting instructions and session context configuration.readthis connector
fullstory.extraction_rules.createCreate Extraction RuleCreates a single extraction rule. The rule begins capturing data immediately after creation.writethis connector
fullstory.summary_profiles.createCreate ProfileCreate the session summary prompt profile that specifies both prompting instructions and session context configuration. See [the Generate Summary Overview…writethis connector
fullstory.element_block_rules.createCreate Element Block RuleCreates a new element block rule. If the rule targets a mobile platform and uses a descendant selector, a backup_selector is automatically generated for…writethis connector

Try it

Prompts to paste into Claude.

Each one names the Fullstory actions it will call, so you know what it reads and what it changes before you send it.

  1. Readread

    Find the Fullstory contacts with no email address, so we can clean them up.

    callsfullstory.users.list

  2. Writewrite

    Create Event in Fullstory. Show me exactly what you will send before you save it.

    callsfullstory.events.create

  3. Across systemsread

    Which contacts are in both Fullstory and HaloPSA, and how many are in only one of them?

    callsfullstory.users.listhalopsa.users.list

Across your systems

Fullstory, joined to the rest of your business.

One ask fetches from Fullstory and another system, joins the rows on the same customer on our side, and hands your agent the answer, not every row.

  • Which contacts are in both Fullstory and HaloPSA, and how many are in only one of them?

    fullstory.users.list + halopsa.users.list, on crm.contact · HaloPSA

  • Which contacts are in both Fullstory and NetSuite, and how many are in only one of them?

    fullstory.users.list + netsuite.views.contacts, on crm.contact · NetSuite

Also mapped by other connectorscrm.contact 192
ask
ask {  intent: "which contacts are in both Fullstory and HaloPSA, and how many are in only one of them",  steps: [    { action: "fullstory.users.list", as: "people", input: {}, limit: 100, max_pages: 5 },    { action: "halopsa.users.list", as: "people2", input: {}, limit: 100, max_pages: 5 },    { join: {        left: "people",        right: "people2",        on: "crm.contact",        group_by: "people.email",        select: ["people.email", "count(people2.id) as in_halopsa"]    } }  ]}
Example. Run it through check first: it validates the steps and prices them, and it is free.

Governance for Fullstory

Destructive actions wait for a yes.

5 Fullstory actions are destructive. These are all of them:

  • Delete Userfullstory.users.delete
  • Deletefullstory.summary_profiles.delete
  • Delete Element Block Rulefullstory.element_block_rules.delete
  • Delete Userfullstory.v1.users.delete
  • Cancel Operationfullstory.v1.operations.cancel

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

dofullstory.users.deleteconfirm_policy: human

Delete User?

intent: the user asked me to delete User

run suspended · waiting for a named person · key fullstory-agent cannot confirm itself
In the console, or from an emailed signed link.
a key for this connector
account {  op: "keys.create", name: "fullstory-agent",  allowed_actions: ["fullstory.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "fullstory.users.delete", approver: "[email protected]" },    { match: "fullstory.summary_profiles.delete", approver: "[email protected]" },    { match: "fullstory.element_block_rules.delete", approver: "[email protected]" }  ]}
Illustrative. Scoped to Fullstory only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What Fullstory costs on actionlake.

Every Fullstory action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Fullstory refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

  • 1upstream call per actionall 68 Fullstory actions
  • 68actions pageeach page of a long list is one call
  • 35reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Fullstory action.

68 actions by area: the id your agent calls, what it does, and its effect.

Users15
  • fullstory.users.batch_imports.createCreate Batch User Import Jobwrite
  • fullstory.users.batch_imports.errors.listGet Batch User Import Errorsread
  • fullstory.users.batch_imports.getGet Batch User Import Statusread
  • fullstory.users.batch_imports.results.listGet Batch User Importsread
  • fullstory.users.createCreate Userwrite
  • fullstory.users.deleteDelete Userdestructive
  • fullstory.users.getGet Userread
  • fullstory.users.listList Usersread
  • fullstory.users.stream.createCreate User Streamwrite
  • fullstory.users.stream.getGet Create User Stream Statusread
  • fullstory.users.updateUpdate Userwrite
  • fullstory.v1.users.custom_events.createSet User Eventswrite
  • fullstory.v1.users.custom_vars.updateSet User Propertieswrite
  • fullstory.v1.users.deleteDelete Userdestructive
  • fullstory.v1.users.getGet Userread
Settings13
  • fullstory.v1.settings.blocking.getGet Recording Block Rulesread
  • fullstory.v1.settings.blocking.history.listGet Recording Block Rules Historyread
  • fullstory.v1.settings.domain.getGet Domain Settingsread
  • fullstory.v1.settings.domain.history.listGet Domain Settings Historyread
  • fullstory.v1.settings.features.getGet Recording Featuresread
  • fullstory.v1.settings.features.history.listGet Recording Features Historyread
  • fullstory.v1.settings.geo.getGet Geo Settingsread
  • fullstory.v1.settings.geo.history.listGet Geo Settings Historyread
  • fullstory.v1.settings.privacy.element_block_rules.updateUpdate Element Block Ruleswrite
  • fullstory.v1.settings.privacy.getGet Privacy Settingsread
  • fullstory.v1.settings.privacy.history.listGet Privacy Settings Historyread
  • fullstory.v1.settings.targeting.getGet Targeting Settingsread
  • fullstory.v1.settings.targeting.history.listGet Targeting Settings Historyread
Extraction rules7
  • fullstory.extraction_rules.archiveArchive Extraction Rulewrite
  • fullstory.extraction_rules.createCreate Extraction Rulewrite
  • fullstory.extraction_rules.getGet Extraction Ruleread
  • fullstory.extraction_rules.listList Extraction Rulesread
  • fullstory.extraction_rules.patchUpdate Extraction Rulewrite
  • fullstory.extraction_rules.replaceUpdate Extraction Rule Putwrite
  • fullstory.extraction_rules.unarchiveUnarchive Extraction Rulewrite
Sessions6
  • fullstory.sessions.context.generateGenerate Contextwrite
  • fullstory.sessions.events.listGet Session Eventsread
  • fullstory.sessions.listList Sessionsread
  • fullstory.sessions.summary.generateGenerate Summary With Overrideswrite
  • fullstory.sessions.summary.getGenerate Summaryread
  • fullstory.v1.sessions.listList Sessionsread
Element block rules5
  • fullstory.element_block_rules.createCreate Element Block Rulewrite
  • fullstory.element_block_rules.deleteDelete Element Block Ruledestructive
  • fullstory.element_block_rules.getGet Element Block Ruleread
  • fullstory.element_block_rules.listList Element Block Rulesread
  • fullstory.element_block_rules.updateUpdate Element Block Rulewrite
Events5
  • fullstory.events.batch_imports.createCreate Batch Events Import Jobwrite
  • fullstory.events.batch_imports.errors.listGet Batch Events Import Errorsread
  • fullstory.events.batch_imports.getGet Batch Events Import Statusread
  • fullstory.events.batch_imports.results.listGet Batch Events Importsread
  • fullstory.events.createCreate Eventwrite
Summary profiles5
  • fullstory.summary_profiles.createCreate Profilewrite
  • fullstory.summary_profiles.deleteDeletedestructive
  • fullstory.summary_profiles.getGetread
  • fullstory.summary_profiles.listList Profilesread
  • fullstory.summary_profiles.updateUpdatewrite
Operations3
  • fullstory.v1.operations.cancelCancel Operationdestructive
  • fullstory.v1.operations.getGet Operation Statusread
  • fullstory.v1.operations.listList Operationsread
Segments3
  • fullstory.v1.segments.exports.createCreate Segment Exportwrite
  • fullstory.v1.segments.getGet Segmentread
  • fullstory.v1.segments.listList Segmentsread
Annotations1
  • fullstory.annotations.createCreate Annotationwrite
Datasets1
  • fullstory.datasets.listList Datasetsread
Exports1
  • fullstory.v1.exports.listList Event Exportsread
Me1
  • fullstory.me.getMeread
Organization1
  • fullstory.organization.quotas.getGet Quotasread
Search exports1
  • fullstory.v1.search_exports.results.getGet Search Export Resultsread

Questions

The Fullstory MCP server, answered.

Is there a Fullstory MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 68 Fullstory actions across users, settings, extraction rules and sessions, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Fullstory.

What do I need to connect Fullstory?

Fullstory API key (Settings > Integrations > API Keys. The free call account { op: "connections.requirements", service: "fullstory" } lists exactly what to paste.

Can an AI agent delete or change things in Fullstory?

Only if its key allows it, and only with an explicit confirmation. 5 Fullstory actions are destructive, including delete User, delete and delete Element Block Rule. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my Fullstory API limit?

actionlake paces every call to the limits in the Fullstory service file: 300 calls a minute per connection. Repeated reads are answered from cache (35 Fullstory actions can be), which never reaches Fullstory.

What does a Fullstory action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (68 Fullstory actions page). Cache hits, searches, dry runs and calls Fullstory refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which Fullstory API does it cover?

The Fullstory Server API v2 (+ v2beta and the v1 endpoints still documented) at api.fullstory.com. It is built from Fullstory's documentation as read on 23 October 2026. 68 actions in 15 areas, each one in the signed service file (version 1.0.0).

Can I combine Fullstory with my other systems?

Yes. ask joins Fullstory to HaloPSA or NetSuite on the same customer and returns the answer rather than every row. Fullstory maps crm.contact, which 192 other connectors also map.

Does actionlake keep my Fullstory data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to an hour, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Fullstory credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

More connectors like Fullstory

Shares the most action names with

Joins with, on shared entities

Browse

actionlake is independent. It is not made or endorsed by Fullstory; the name is the vendor's own. Counts are from the Fullstory service file, version 1.0.0.

Give your agent Fullstory today.

Connect Fullstory freeSee pricing

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.