100+ integrations are ready to connect to your AI.Connect your first MCP

FullStory MCP server for your AI

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

Find jen@example.com and tell me what happened in her latest session

Supported FullStory tools

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_import

See whether a batch import has finished, with counts and failures.

fullstory_create_user

Create an user or update the one with the same uid.

fullstory_delete_user

PERMANENTLY delete one user and their data, by FullStory's id.

fullstory_delete_user_by_uid

PERMANENTLY delete one user and their data, by your own uid.

fullstory_find_user

Find an user from an email, uid or FullStory id, with their latest sessions.

fullstory_get_user

One user by FullStory's own id.

fullstory_get_user_by_uid

One identified user by your own uid: name, email, custom vars, session count, first and last seen.

fullstory_import_users

Create or update many users, wait, and report what worked and what failed.

fullstory_list_users

Find users by uid, email, display_name or is_identified.

fullstory_update_user

Change an user's uid, display_name, email or properties, by FullStory's id.

fullstory_get_privacy_settings

The current privacy settings: elements excluded, masked or unmasked, and which network bodies are recorded.

fullstory_get_recording_features

Whether recording is on, and whether console, network and resource capture are on.

fullstory_generate_session_context

A session's pages and events, trimmed for an AI to read.

fullstory_generate_session_summary

FullStory's AI summary of one session with your own instructions for this call.

fullstory_get_session_events

Every event captured in one session, raw and large (at most 500 are shown).

fullstory_get_session_summary

FullStory's AI summary of one session.

fullstory_list_sessions

A user's most recent sessions, each with its id, app_url (the replay link) and created_time.

fullstory_list_summary_profiles

The saved session summary profiles (prompts and settings).

fullstory_create_webhook_endpoint

Send FullStory events to a URL of yours.

fullstory_list_webhook_endpoints

The webhook endpoints set up in FullStory, with their URL and events.

fullstory_list_webhook_event_types

The event types this plan can send, and whether each needs a subcategory.

fullstory_check_export

See whether an export has finished, and get its link and first rows.

fullstory_export_segment

Export a segment's people or events: start, wait, get the link and first rows.

fullstory_find_segment

Find saved segments by part of their name.

fullstory_get_segment

One segment by id.

fullstory_list_segments

Saved segments, with id, name, creator, created and url.

fullstory_create_event

Record one event that happened outside the browser, such as a refund or a CRM change.

fullstory_import_events

Record many events, wait, and report what worked and what failed.

fullstory_draft_analytics_object

Build or change a draft segment, metric, funnel or journey from a plain description.

fullstory_get_operation

One background job's state, percent complete and results.

fullstory_list_analytics_tools

List the metric, funnel, journey and session review tools on FullStory's own MCP server.

fullstory_run_analytics_tool

Run a metric, funnel, journey, frustration or session review tool that only reads.

fullstory_create_annotation

Mark a moment on FullStory's charts, such as a release or a campaign launch.

fullstory_get_api_key_info

Check this connection's key: the organization id and role.

fullstory_get_quotas

How much of this period's session and server event quota is used, with limits and period dates.

fullstory_create_user_async

Create or update an user without waiting.

fullstory_get_user_async_status

The result of fullstory_create_user_async, by its request_id.

fullstory_get_user_import_status

A user import job's status (PROCESSING, COMPLETED or FAILED) and its counts.

fullstory_list_user_import_errors

The users an import job could not import, each with a message and code.

fullstory_list_user_import_results

The users a finished import job created or updated, with FullStory's id for each.

fullstory_start_user_import

Start a batch import of users and return a job.

fullstory_get_domain_settings

Which domains FullStory records, and whether it records only those.

fullstory_get_geo_settings

Which countries and regions FullStory records.

fullstory_get_recording_block_rules

The IP addresses, user agents and app ids FullStory will not record.

fullstory_get_targeting_settings

The rules that decide which sessions FullStory records.

fullstory_list_domain_settings_history

Past versions of the domain settings, for audits, newest first, with who changed them.

fullstory_list_geo_settings_history

Past versions of the geo settings, for audits, newest first, with who changed them.

fullstory_list_privacy_settings_history

Past versions of the privacy settings, for audits, newest first, with who changed them.

fullstory_list_recording_block_rules_history

Past versions of the recording block rules, for audits, newest first, with who changed them.

fullstory_list_recording_features_history

Past versions of the recording features, for audits, newest first, with who changed them.

fullstory_list_targeting_settings_history

Past versions of the targeting rules, for audits, newest first, with who changed them.

fullstory_update_element_block_rules

Add, change or remove privacy rules for page elements.

fullstory_create_summary_profile

Save a session summary profile.

fullstory_delete_summary_profile

Delete a saved session summary profile.

fullstory_get_summary_profile

One session summary profile, by its id from fullstory_list_summary_profiles.

fullstory_update_summary_profile

Change a saved session summary profile.

fullstory_delete_webhook_endpoint

Delete a webhook endpoint.

fullstory_get_webhook_endpoint

One webhook endpoint, by its id from fullstory_list_webhook_endpoints.

fullstory_get_webhook_sample

A sample payload for one event type, so you can see what your endpoint will receive.

fullstory_list_webhook_event_subcategories

The subcategories of one event type, such as segment.trend.alert.

fullstory_update_webhook_endpoint

Change a webhook endpoint's url, event_types or secret, or set disabled: true to pause it.

fullstory_archive_extraction_rule

Stop a rule capturing and free its slot.

fullstory_create_extraction_rule

Create a rule that captures data right away.

fullstory_create_segment_export

Schedule an export of a segment's people or events.

fullstory_get_export_results

A temporary download link for a finished export.

fullstory_get_extraction_rule

One extraction rule, by its id from fullstory_list_extraction_rules.

fullstory_list_extraction_rules

Rules that turn page content, URLs or network calls into properties, with usage per scope.

fullstory_replace_extraction_rule

Replace a whole extraction rule.

fullstory_unarchive_extraction_rule

Restart an archived rule.

fullstory_update_extraction_rule

Change part of an extraction rule: name, description, source or mappings.

fullstory_get_event_import_status

An event import job's status (PROCESSING, COMPLETED or FAILED) and its counts.

fullstory_list_event_import_errors

The events an import job refused, each with a message and code.

fullstory_list_event_import_results

The events a finished import job accepted.

fullstory_start_event_import

Start a batch import of events and return a job.

fullstory_create_element_block_rule

Add a privacy rule for page elements.

fullstory_delete_element_block_rule

Delete a custom element privacy rule.

fullstory_get_element_block_rule

One element privacy rule, by its id from fullstory_list_element_block_rules.

fullstory_list_element_block_rules

Privacy rules for page elements, both custom and built in.

fullstory_update_element_block_rule

Change an element privacy rule.

fullstory_cancel_operation

Cancel a running segment export.

fullstory_list_operations

Background jobs (exports and user deletions), running and finished.

fullstory_delete_user_by_uid_v1

PERMANENTLY delete everything FullStory holds on an user, by your own uid: sessions, events, custom vars and page files.

fullstory_get_user_events

The events FullStory recorded for one user, by your own uid.

fullstory_get_user_pages

The pages one user visited, by your own uid, with raw event data for each page.

fullstory_list_sessions_legacy

The older form of fullstory_list_sessions, with user_id, session_id, created_time and fs_url.

fullstory_list_datasets

The datasets this key can read.

Connect FullStory to Claude, ChatGPT and Claude Code

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.

API key••••••••••••3f7a
ConnectionVerified

Then just ask for the work

  • “Find jen@example.com and tell me what happened in her latest session”

    • find_user
    • get_session_summary
  • “Why did this person stop at checkout? Here is the replay link”

    • generate_session_summary
  • “What are the top frustrations on our pricing page this week?”

    • list_analytics_tools
    • run_analytics_tool
  • “Build a funnel from the cart to order confirmed and show me where people drop off”

    • draft_analytics_object
    • run_analytics_tool
  • “Export everyone in our Churned Customers segment from last month to a file”

    • find_segment
    • export_segment
  • “Add a chart marker for today's checkout redesign release”

    • create_annotation
  • “Record a Refund issued event on user 4417 from our billing system”

    • create_event
  • “We have a confirmed deletion request. Delete everything FullStory holds on user 4417”

    • delete_user_by_uid

Use FullStory from the assistant you already open

One hosted endpoint, registered once per client. The same tools and the same permissions, whichever window the request comes from.

Claude DesktopCustom connector

Add the PopMCP URL under Customize → Connectors and the tools appear in every chat.

Claude WebCustom connector

The same endpoint, registered in the browser. Nothing to install on the machine you are working from.

ChatGPTCustom connector

Register PopMCP as a custom connector, then let ChatGPT read and update the account.

CodexDesktop & CLI

Wire the endpoint into Codex or the Codex CLI when a task needs live business context, not a fixture.

OpenCodeCoding agent

Register the remote MCP server in OpenCode's config for terminal-first and scripted agent runs.

ZCodeDesktop app

Add PopMCP as an MCP server in Z.ai's desktop app and work the account from the same window.

FullStory MCP server questions

What teams ask before putting FullStory behind an AI client.

What does the FullStory MCP server need to connect?

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.

Which permission level should the key have?

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.

Can my AI see metrics and funnels?

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.

Can my AI watch a session replay?

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.

Do session summaries cost anything?

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.

Can I export data from FullStory?

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.

Does it work with FullStory's EU data center?

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.

Can a deletion be undone?

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.

Do I have to run or host the FullStory MCP server myself?

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.

Which AI clients can use this MCP server?

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.

How do I connect FullStory to Claude Code?

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.

Why do only 35 of the 86 tools load by default?

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.

What is the difference between a tool and a trigger?

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.

Connect FullStory to your AI in minutes

Launch a hosted MCP endpoint for FullStory, keep tool access under control, and start testing real workflow prompts right away.

Connect your first MCP