What does a Fullstory MCP server do?
The Fullstory MCP server lets an AI assistant query your behavioral data. It builds and runs metrics, segments, funnels and journeys, pulls sessions and reads their event transcripts. Agentic session review captures screenshots at a timestamp, so the assistant can see what a user saw. Your privacy rules still apply, including masking and exclusions.
- Fullstory for Customer Agents: a separate read-only server at
https://api.fullstory.com/mcp/activationsgives support and sales agents context on one session. Fullstory points aggregate analytics to the main server. - Skills: the
fullstory-skillsplugin adds skills and a session-context agent on top of the same tools.
Is there an official Fullstory MCP server?
Yes. Fullstory publishes the server and its docs, and its release notes show a beta in April 2026 and general availability in October 2026. Claude's directory lists the connector as made by Fullstory. Fullstory also maintains the fullstory-skills plugin on its own GitHub org.
- Fullstory's FAQ still says "during Early Access" where it explains manual saving. The October release notes are the later statement.
What is the Fullstory MCP server URL, and how do you sign in?
The URL is https://api.fullstory.com/mcp/fullstory. You sign in with OAuth in a browser as yourself. An API key suits gateways and shared services, sent as a Bearer token, and Fullstory recommends a Standard key. Some clients need the regional URL: https://api.eu1.fullstory.com/mcp/fullstory for EU orgs or https://api.na1.fullstory.com/mcp/fullstory for US orgs.
- StoryAI and the Model Context Protocol toggle must both be on, under Settings > StoryAI Features. If StoryAI is opted out, the client shows as connected with no tools.
- Fullstory says all orgs have MCP on by default.
- Each connection covers one org, so several orgs need several connections.
What can a Fullstory MCP server read and change?
Most tools read. The build_ tools turn a description into a segment, metric, funnel or journey. Fullstory's tools reference says segments, funnels and journeys persist, while its limits page says the server only creates drafts that need a manual save. Check your org after a build. Users, billing and settings stay out of reach.
What it can read
- Metrics and segments:
compute_metric,get_metric,get_segmentandget_view_counts. - Funnels and journeys:
compute_funnel,get_funnel_sessions,compute_journeyandget_journey_sessions. - Sessions:
get_sessions,get_session_eventsandget_pages. - Session review:
review-open,review-snapshot,review-zoom,review-summaryandreview-close. - Frustration signals:
discover_groupsandget_opportunity_stats.get_opportunitiesand the other lookup tools need the StoryAI Premium SKU.
What it can change
- Segments:
build_segmentpersists a segment and returns itssegment_id.update_segmentrefines one. - Funnels and journeys:
build_funnelandbuild_journeypersist a definition. Theupdate_tools produce a refined copy and leave the source unchanged. - Metrics:
build_metricandupdate_metriccreate definitions. Fullstory's FAQ says unsaved segments and metrics are discarded when the session ends.
How do you set up a Fullstory MCP server in Claude, ChatGPT and Cursor?
Fullstory documents all three as listed installs. Claude uses the connector directory, ChatGPT and Codex use the plugin directory, and Cursor uses the plugin marketplace. Each route signs in with OAuth. Check that StoryAI is on first, because the client connects with no tools if it's off.
Claude
Fullstory lists a connector in Claude's directory and documents these steps.
- Open Customize in the left sidebar, then Connectors.
- Choose Add, then Browse Connectors, and search for Fullstory.
- Select Connect to Claude and authorize with Fullstory.
- In a new chat, ask: What Fullstory tools are available?
- In Claude Code, use the plugin marketplace: run
/plugin marketplace add fullstorydev/fullstory-skills, then/plugin install fullstory@fullstory.
ChatGPT
Fullstory documents a plugin in the ChatGPT directory. The same install turns it on in Codex.
- Click Explore, then Plugins, search for Fullstory and click +.
- Click Install plugin and sign in to Fullstory.
- Review the requested permissions and click Approve.
- Click Try now.
Cursor
Fullstory documents a Cursor Marketplace plugin.
- Run
/add-plugin fullstoryin an agent chat, or open the plugin in the Cursor marketplace. - Click + Add to Cursor, then Add Plugin.
- Open the plugin, click Authenticate, review the permissions and click Approve.
- Open a new agent chat.
What can you ask a Fullstory MCP server?
Good first prompts name a page, a date range and a comparison. These examples follow Fullstory's release impact workflow and use tools it documents. Keep session pulls small, since session tools stop at 50. Prompts that build a segment, metric or funnel can create objects, so check what the assistant made.
Reads
Compare frustration signals on the checkout page in the 7 days after our release with the 7 days before. What got worse?
Reads
Pull 3 sessions where users rage-clicked the shipping step. What's the common pattern?
Reads
Open that session and take a snapshot at the moment the user gave up. What did they see?
Writes
Build a funnel from the pricing page to signup complete, then compare conversion by step. Tell me what you saved.
Writes
Build a metric tracking rage clicks on the shipping step as a daily trend, and give me the link so I can save it.
What are the limits of a Fullstory MCP server?
Fullstory limits the server to 3 requests a second, with a burst of 20, per org and per endpoint. Session tools default to 10 and stop at 50. Group-by results stop at 50 rows, so Fullstory says it doesn't suit bulk exports. It covers part of the product, focused on metrics, segments and session replay.
- Each server connects to one org, and cross-org queries aren't supported.
- Fullstory doesn't schedule queries. Scheduling depends on your AI client, and rate limits still apply.
- MCP rate limits are tracked separately from Server API limits.
How much does a Fullstory MCP server cost?
Fullstory lists no separate price for the server, and it's available to all paying customers. Fullstory shows no public prices for Business, Advanced or Enterprise, so you request a quote. FullstoryFree costs nothing but leaves out StoryAI, which the server needs. Four lookup tools also need the StoryAI Premium SKU.
- FullstoryFree includes 30,000 sessions a month, 12 months of retention and up to 10 users.
- Fullstory for Customer Agents is part of Anywhere: Activation, with 1,000 Activations a month on Enterprise and Advanced plans. Each tool call uses Activations.
What are the alternatives to a Fullstory MCP server?
The main alternatives are another behavior tool's server or a product analytics server. Product analytics MCP servers compared covers Amplitude, Mixpanel, PostHog, Pendo and Contentsquare side by side, so you can match the server to the tool that holds your trusted numbers. Each option below is a separate product.
- Microsoft Clarity MCP: Site behavior metrics, if you run Clarity beside or instead of Fullstory.
- Pendo MCP: Usage, guides and feedback, if Pendo holds your product data.
- Amplitude MCP: The route if Amplitude holds your product analytics.
- PostHog MCP: The route if PostHog holds your product analytics.
Which skill goes with a Fullstory MCP server?
Use the free Agent write safety skill before you let an assistant build segments, funnels or journeys, because those can land in your Fullstory org. Use the Analytics tool selector to decide whether Fullstory or a product analytics tool should answer a question, so you connect the server that holds the right data.
- Agent write safety: Sets approvals before an agent can create objects in your org.
- Analytics tool selector: Helps you choose which analytics tool should answer each question.
We set up Claude Code and MCP for marketing teams, with access scoped per person and approval before anything changes.
Sources
- Fullstory: Fullstory MCP introduction
- Fullstory: Authentication
- Fullstory: Tools Reference
- Fullstory: Limits and what's not supported yet
- Fullstory: FAQ and troubleshooting
- Fullstory: Claude setup
- Fullstory: Claude Code setup
- Fullstory: Codex and ChatGPT setup
- Fullstory: Cursor setup
- Fullstory: Release impact, before vs. after
- Fullstory: Fullstory Release Notes
- Fullstory: Fullstory MCP help article
- Fullstory: Fullstory for Customer Agents, MCP integration
- Fullstory: Plans and pricing
- Fullstory: fullstorydev/fullstory-skills
- Anthropic: Fullstory connector in the Claude directory