fullstory_check_ importSee whether a batch import has finished, with counts and failures.
Ask what a customer did before they gave up, see where a funnel leaks, summarize a session without watching it, or send your own events to FullStory, all from your AI.
PopMCPFullStory
Every endpoint in FullStory's Server API, plus FullStory's own tools for metrics, funnels, journeys and session review, on one connection. Your AI can find a person from an email, read their sessions, and pull a segment into a file in one step.
86 tools in the full catalog: 57 read and 29 write. 35 load by default, and the rest are found with tool search.
fullstory_check_ importSee whether a batch import has finished, with counts and failures.
fullstory_create_ userCreate an user or update the one with the same uid.
fullstory_delete_ userPERMANENTLY delete one user and their data, by FullStory's id.
fullstory_delete_ user_ by_ uidPERMANENTLY delete one user and their data, by your own uid.
fullstory_find_ userFind an user from an email, uid or FullStory id, with their latest sessions.
fullstory_get_ userOne user by FullStory's own id.
fullstory_get_ user_ by_ uidOne identified user by your own uid: name, email, custom vars, session count, first and last seen.
fullstory_import_ usersCreate or update many users, wait, and report what worked and what failed.
fullstory_list_ usersFind users by uid, email, display_name or is_identified.
fullstory_update_ userChange an user's uid, display_name, email or properties, by FullStory's id.
fullstory_get_ privacy_ settingsThe current privacy settings: elements excluded, masked or unmasked, and which network bodies are recorded.
fullstory_get_ recording_ featuresWhether recording is on, and whether console, network and resource capture are on.
fullstory_generate_ session_ contextA session's pages and events, trimmed for an AI to read.
fullstory_generate_ session_ summaryFullStory's AI summary of one session with your own instructions for this call.
fullstory_get_ session_ eventsEvery event captured in one session, raw and large (at most 500 are shown).
fullstory_get_ session_ summaryFullStory's AI summary of one session.
fullstory_list_ sessionsA user's most recent sessions, each with its id, app_url (the replay link) and created_time.
fullstory_list_ summary_ profilesThe saved session summary profiles (prompts and settings).
fullstory_create_ webhook_ endpointSend FullStory events to a URL of yours.
fullstory_list_ webhook_ endpointsThe webhook endpoints set up in FullStory, with their URL and events.
fullstory_list_ webhook_ event_ typesThe event types this plan can send, and whether each needs a subcategory.
fullstory_check_ exportSee whether an export has finished, and get its link and first rows.
fullstory_export_ segmentExport a segment's people or events: start, wait, get the link and first rows.
fullstory_find_ segmentFind saved segments by part of their name.
fullstory_get_ segmentOne segment by id.
fullstory_list_ segmentsSaved segments, with id, name, creator, created and url.
fullstory_create_ eventRecord one event that happened outside the browser, such as a refund or a CRM change.
fullstory_import_ eventsRecord many events, wait, and report what worked and what failed.
fullstory_draft_ analytics_ objectBuild or change a draft segment, metric, funnel or journey from a plain description.
fullstory_get_ operationOne background job's state, percent complete and results.
fullstory_list_ analytics_ toolsList the metric, funnel, journey and session review tools on FullStory's own MCP server.
fullstory_run_ analytics_ toolRun a metric, funnel, journey, frustration or session review tool that only reads.
fullstory_create_ annotationMark a moment on FullStory's charts, such as a release or a campaign launch.
fullstory_get_ api_ key_ infoCheck this connection's key: the organization id and role.
fullstory_get_ quotasHow much of this period's session and server event quota is used, with limits and period dates.
fullstory_create_ user_ asyncCreate or update an user without waiting.
fullstory_get_ user_ async_ statusThe result of fullstory_create_user_async, by its request_id.
fullstory_get_ user_ import_ statusA user import job's status (PROCESSING, COMPLETED or FAILED) and its counts.
fullstory_list_ user_ import_ errorsThe users an import job could not import, each with a message and code.
fullstory_list_ user_ import_ resultsThe users a finished import job created or updated, with FullStory's id for each.
fullstory_start_ user_ importStart a batch import of users and return a job.
fullstory_get_ domain_ settingsWhich domains FullStory records, and whether it records only those.
fullstory_get_ geo_ settingsWhich countries and regions FullStory records.
fullstory_get_ recording_ block_ rulesThe IP addresses, user agents and app ids FullStory will not record.
fullstory_get_ targeting_ settingsThe rules that decide which sessions FullStory records.
fullstory_list_ domain_ settings_ historyPast versions of the domain settings, for audits, newest first, with who changed them.
fullstory_list_ geo_ settings_ historyPast versions of the geo settings, for audits, newest first, with who changed them.
fullstory_list_ privacy_ settings_ historyPast versions of the privacy settings, for audits, newest first, with who changed them.
fullstory_list_ recording_ block_ rules_ historyPast versions of the recording block rules, for audits, newest first, with who changed them.
fullstory_list_ recording_ features_ historyPast versions of the recording features, for audits, newest first, with who changed them.
fullstory_list_ targeting_ settings_ historyPast versions of the targeting rules, for audits, newest first, with who changed them.
fullstory_update_ element_ block_ rulesAdd, change or remove privacy rules for page elements.
fullstory_create_ summary_ profileSave a session summary profile.
fullstory_delete_ summary_ profileDelete a saved session summary profile.
fullstory_get_ summary_ profileOne session summary profile, by its id from fullstory_list_summary_profiles.
fullstory_update_ summary_ profileChange a saved session summary profile.
fullstory_delete_ webhook_ endpointDelete a webhook endpoint.
fullstory_get_ webhook_ endpointOne webhook endpoint, by its id from fullstory_list_webhook_endpoints.
fullstory_get_ webhook_ sampleA sample payload for one event type, so you can see what your endpoint will receive.
fullstory_list_ webhook_ event_ subcategoriesThe subcategories of one event type, such as segment.trend.alert.
fullstory_update_ webhook_ endpointChange a webhook endpoint's url, event_types or secret, or set disabled: true to pause it.
fullstory_archive_ extraction_ ruleStop a rule capturing and free its slot.
fullstory_create_ extraction_ ruleCreate a rule that captures data right away.
fullstory_create_ segment_ exportSchedule an export of a segment's people or events.
fullstory_get_ export_ resultsA temporary download link for a finished export.
fullstory_get_ extraction_ ruleOne extraction rule, by its id from fullstory_list_extraction_rules.
fullstory_list_ extraction_ rulesRules that turn page content, URLs or network calls into properties, with usage per scope.
fullstory_replace_ extraction_ ruleReplace a whole extraction rule.
fullstory_unarchive_ extraction_ ruleRestart an archived rule.
fullstory_update_ extraction_ ruleChange part of an extraction rule: name, description, source or mappings.
fullstory_get_ event_ import_ statusAn event import job's status (PROCESSING, COMPLETED or FAILED) and its counts.
fullstory_list_ event_ import_ errorsThe events an import job refused, each with a message and code.
fullstory_list_ event_ import_ resultsThe events a finished import job accepted.
fullstory_start_ event_ importStart a batch import of events and return a job.
fullstory_create_ element_ block_ ruleAdd a privacy rule for page elements.
fullstory_delete_ element_ block_ ruleDelete a custom element privacy rule.
fullstory_get_ element_ block_ ruleOne element privacy rule, by its id from fullstory_list_element_block_rules.
fullstory_list_ element_ block_ rulesPrivacy rules for page elements, both custom and built in.
fullstory_update_ element_ block_ ruleChange an element privacy rule.
fullstory_cancel_ operationCancel a running segment export.
fullstory_list_ operationsBackground jobs (exports and user deletions), running and finished.
fullstory_delete_ user_ by_ uid_ v1PERMANENTLY delete everything FullStory holds on an user, by your own uid: sessions, events, custom vars and page files.
fullstory_get_ user_ eventsThe events FullStory recorded for one user, by your own uid.
fullstory_get_ user_ pagesThe pages one user visited, by your own uid, with raw event data for each page.
fullstory_list_ sessions_ legacyThe older form of fullstory_list_sessions, with user_id, session_id, created_time and fs_url.
fullstory_list_ datasetsThe datasets this key can read.
Credentials off one FullStory screen, then an endpoint your client signs into. Nothing to deploy, and nothing to install.
In FullStory open Settings, then Integrations, then API Keys, click Create key and choose Admin so every tool works. Paste the key into PopMCP. It is one value: your organization and data center come from the key.
••••••••••••3f7aReading users, sessions, metrics and settings is open from the start. Sending events, changing users, building drafts and changing privacy rules are writes and wait until an owner or admin allows write actions; new connections start read-only. Deleting a user also needs an explicit confirmation in the call. Tick FullStory on the PopMCP consent screen only for clients that need it.
Drop the PopMCP URL into Claude, ChatGPT, Claude Code, Codex or any other supported client. It signs in through PopMCP with OAuth, so your FullStory credential never leaves the server.
app.popmcp.com/mcpAsk for something harmless before the agent changes anything. Writes run as soon as it calls them, so confirm it reads the right account first.
Find jen@example.com and tell me what happened in her latest session
fullstory_find_userok
Then just ask for the work
“Find jen@example.com and tell me what happened in her latest session”
“Why did this person stop at checkout? Here is the replay link”
“What are the top frustrations on our pricing page this week?”
“Build a funnel from the cart to order confirmed and show me where people drop off”
“Export everyone in our Churned Customers segment from last month to a file”
“Add a chart marker for today's checkout redesign release”
“Record a Refund issued event on user 4417 from our billing system”
“We have a confirmed deletion request. Delete everything FullStory holds on user 4417”
One hosted endpoint, registered once per client. The same tools and the same permissions, whichever window the request comes from.
Add the PopMCP URL under Customize → Connectors and the tools appear in every chat.
The same endpoint, registered in the browser. Nothing to install on the machine you are working from.
Register PopMCP as a custom connector, then let ChatGPT read and update the account.
Wire the endpoint into Codex or the Codex CLI when a task needs live business context, not a fixture.
Register the remote MCP server in OpenCode's config for terminal-first and scripted agent runs.
Add PopMCP as an MCP server in Z.ai's desktop app and work the account from the same window.
FAQ
What teams ask before putting FullStory behind an AI client.
One API key. Make it in FullStory under Settings, then Integrations, then API Keys, and paste it into PopMCP. There is no app to review and nothing to deploy. FullStory shows a key only once, so copy it straight away. A key belongs to one organization.
Admin lets every tool work, and only an Admin can make one. Architect reads, exports and deletes user data, and needs an Enterprise plan. Standard sends data, lists sessions and reads recording settings. When a tool needs more, its answer names the level and says what your key has.
Yes, through FullStory's own AI tools, which PopMCP reaches with the same key. They cover metrics, funnels, journeys, frustration signals and session review. An Admin must turn on StoryAI and the Model Context Protocol switch at Settings, Account Management, StoryAI Features. PopMCP tells you when they connect if they are off.
Not as video. It reads what happened instead: the pages and events in a session, FullStory's AI summary of it, and a replay link you can open yourself. It can also take a snapshot of the screen at a moment through FullStory's session review tools, when StoryAI is on.
They count against your plan's Activation quota. Reading a session's events, generating its context and generating its summary each use one Activation, and this is part of FullStory's Anywhere: Activation. Finding a person and listing their sessions does not use any.
Yes. Name a segment or use everyone, and PopMCP starts the export, waits, and returns a temporary download link and the first rows. Long date ranges can reach many gigabytes, so it defaults to the last week. Segment Export is an add-on on FullStory's Enterprise and Advanced plans and needs an Architect or Admin key.
Yes, with nothing to set. A key starts with its data center, like eu1, and FullStory routes requests by account. Make the key while signed in at app.eu1.fullstory.com.
No. Deleting a FullStory user removes their sessions and data for good. It needs write actions to be allowed, an Architect or Admin key, and an explicit confirmation in the call, so an AI cannot do it by accident.
No. PopMCP hosts it and gives you a Streamable HTTP MCP URL. There is nothing to deploy, no callback URL to register, and no infrastructure to keep running or patch.
Any client that supports a remote Streamable HTTP MCP server: Claude Desktop, Claude Web, Claude Code, ChatGPT custom connectors, Codex and the Codex CLI, OpenCode and Z.ai's ZCode, as well as editors such as Cursor, Windsurf and Zed. Your client signs in to PopMCP with OAuth; the provider credential never leaves the server.
Connect FullStory in PopMCP first, then run claude mcp add --transport http popmcp https://app.popmcp.com/mcp in a terminal. Inside Claude Code, run /mcp and sign in to PopMCP in the browser window it opens, ticking FullStory on the consent screen. The FullStory tools are then available in that session, and no FullStory credential is stored on your machine.
Loading 86 tool definitions into every conversation burns context before the work starts. PopMCP loads a curated 35-tool set covering the everyday workflows and keeps the rest searchable, so your AI pulls a specialist tool only when a task needs it. Every tool stays searchable, and on Scale the owner can load the full catalog for a teammate's connection.
A tool is something your AI calls, and there are 86 here. A trigger is something PopMCP watches for you: 3 FullStory events that can start work on the PopMCP side. Triggers never enter your AI client's context, and none of them ask you to paste a callback URL into FullStory.
Launch a hosted MCP endpoint for FullStory, keep tool access under control, and start testing real workflow prompts right away.