FullStory MCP server for AI agents and assistants

Securely connect your AI agents and chatbots (Claude, ChatGPT, Cursor, etc) with FullStory MCP or direct API to inspect sessions, analyze events, manage exports, and review recording settings through natural language.

FullStory logoFullStory
Api Key

FullStory is a digital experience analytics platform for tracking user sessions, events, recordings, privacy rules, and organization data. It helps teams understand customer behavior, debug friction, and improve product experiences faster.

30 Tools

Try FullStory now

Type what you want done — sign in and watch it run live in the Tool Router playground.

TOOL ROUTER PLAYGROUND
FullStory
Try asking
TOOLS

Supported Tools

Every FullStory action and event your agent gets out of the box.

Cancel Operation

Irreversibly request cancellation of a cancelable in-progress FullStory operation, currently intended for segment exports.

Create Annotation

Add a persistent annotation to the FullStory timeline for a point or time range.

Create Element Block

Create a beta FullStory element recording or masking rule.

Create Extraction Rule

Create and immediately activate one FullStory beta extraction rule using the provider's nested rule, source, and mapping contract.

Delete Element Block

Permanently delete a custom FullStory privacy element-block rule.

Delete User Data

Permanently delete a FullStory user and their associated data by FullStory-generated ID.

Get FullStory Account

Validate the connected API key and return its FullStory organization, identity, and API-key role.

Get Element Block

Get one FullStory privacy element-block rule by ID, including its exact selector source, recording or masking operation, platforms, and editability.

Get Extraction Rule

Get one FullStory beta extraction rule by ID, including its archive state and complete nested source and mappings.

Get Import Status

Get status and success/error counts for an asynchronous FullStory event or user import job.

Get Operation

Get detailed status, progress, operation-specific results, and failure details for one asynchronous FullStory operation.

Get Organization Quotas

Return current FullStory session and server-event quota usage, limits, and quota periods.

Get Recording Settings

Get one current FullStory recording-settings category.

Get Segment

Get metadata and the FullStory app URL for one segment.

Get User

Retrieve one user by FullStory-generated user ID, including profile fields and a FullStory app link.

Import Events

Start an asynchronous import of 1 to 50,000 server events.

Import Users

Start an asynchronous upsert import of 1 to 50,000 users.

List Datasets

List beta datasets readable by the connected FullStory organization.

List Element Blocks

Return one page of custom and built-in FullStory privacy element-block rules.

List Extraction Rules

List all FullStory beta extraction rules matching one required scope and optional filters, together with current active-rule usage and limits.

List Import Records

Return one page of successful or failed records from a FullStory event or user import job, including failure details when requested.

List Operations

Return one page of asynchronous FullStory operations, optionally filtered by state or type.

List Recording Settings History

Return one page of historical FullStory recording settings for blocking, domain, geo, privacy, features, or targeting.

List Segments

Return one page of FullStory segments, optionally filtered by creator.

List Sessions

Find recent FullStory session replay links by application UID, email, or exact session UID.

Search Users

Find FullStory users by UID, email, display name, or identification state.

Set Extraction Rule Archived

Archive a FullStory beta extraction rule to stop future capture, or unarchive it to resume capture.

Update Element Block

Fully replace an editable beta FullStory element recording or masking rule.

Update Extraction Rule

Partially update a FullStory beta extraction rule using last-write-wins semantics.

Upsert User

Create or update one FullStory user.

SETUP GUIDE

Connect FullStory MCP Tool with your Agent

1

Install Composio

typescript
npm install @composio/core ai @ai-sdk/mcp @ai-sdk/openai
Install the Composio SDK and your agent framework
2

Create a session with MCP enabled

typescript
import { Composio } from "@composio/core";

const composio = new Composio();
const { mcp } = await composio.create("your-user-id", {
  toolkits: ["fullstory"],
  mcp: true,
});
Create a session scoped to FullStory and read its MCP URL and headers
3

Connect your agent to the MCP server

typescript
import { createMCPClient } from "@ai-sdk/mcp";
import { openai } from "@ai-sdk/openai";
import { generateText, stepCountIs } from "ai";

const client = await createMCPClient({
  transport: { type: "http", url: mcp.url, headers: mcp.headers },
});

const { text } = await generateText({
  model: openai("gpt-5.6-sol"),
  tools: await client.tools(),
  prompt: "Find FullStory sessions with JavaScript errors from yesterday",
  stopWhen: stepCountIs(10),
});

console.log(text);
await client.close();
Pass the session's MCP URL and headers to your agent and run a FullStory request
SETUP GUIDE

Connect FullStory API Tool with your Agent

1

Install Composio

typescript
npm install @composio/core @composio/openai openai
Install the Composio SDK, the OpenAI provider, and the OpenAI SDK
2

Create a Composio session

typescript
import OpenAI from "openai";
import { Composio } from "@composio/core";
import { OpenAIResponsesProvider } from "@composio/openai";

const composio = new Composio({ provider: new OpenAIResponsesProvider() });
const client = new OpenAI();

const session = await composio.create("your-user-id", { toolkits: ["fullstory"] });
const tools = await session.tools();
Initialize Composio with the OpenAI Responses provider and create a session scoped to FullStory
3

Run FullStory tools with your agent

typescript
let response = await client.responses.create({
  model: "gpt-5.6-sol",
  tools,
  input: [{ role: "user", content: "Find FullStory sessions with JavaScript errors from yesterday" }],
});

while (response.output.some((o) => o.type === "function_call")) {
  const outputs = await composio.provider.handleToolCalls(session, response.output);
  response = await client.responses.create({
    model: "gpt-5.6-sol",
    tools,
    previous_response_id: response.id,
    input: outputs,
  });
}

console.log(response.output_text);
Send a request, execute the FullStory tool calls through the session, and print the final answer

Why Use Composio?

AI Native FullStory Integration

  • Supports both FullStory MCP and direct API based integrations
  • Structured, LLM-friendly schemas for reliable session, event, and export actions
  • Rich coverage for reading, writing, and querying FullStory experience data

Managed Auth

  • Secure API key handling so agents don't need hard-coded FullStory credentials
  • Central place to manage, scope, and revoke FullStory access
  • Per user and per environment credentials for safer analytics workflows

Agent Optimized Design

  • Tools are tuned for AI agents to understand FullStory users, events, sessions, exports, and recording settings
  • Comprehensive execution logs so you always know what ran, when, and on whose behalf

Enterprise Grade Security

  • Fine-grained RBAC so you control which agents and users can access FullStory
  • Scoped, least privilege access to FullStory organization and analytics resources
  • Full audit trail of agent actions to support review and compliance
FAQ

Frequently asked questions

Yes, FullStory requires you to configure your own API key credentials. Once set up, Composio handles secure credential storage and API request handling for you.

Yes! Composio's Tool Router enables agents to use multiple toolkits. Learn more.

Yes. Composio is SOC 2 Type II compliant and is built to keep your FullStory connection and credentials secure. OAuth tokens and API keys are encrypted, and sensitive customer data is protected at rest and in transit.

Composio also undergoes independent security testing and continuously monitors its systems for security threats. You can review the latest reports and policies in the Composio Trust Center.

Composio maintains and updates all toolkit integrations automatically, so your agents always work with the latest API versions.

Create the key in your FullStory account settings, then paste it once on Composio's connection page. Composio stores it encrypted and uses it only for the FullStory actions your agent runs. Nobody else in your workspace can read it, and you can revoke it inside FullStory at any time.

When you connect a FullStory account through Composio, every action runs under that account, so anything the agent creates, sends, or changes shows up in FullStory as done by you. Keep an approval step in your prompt for actions with side effects, such as sending or deleting, and have the agent draft first.

Whatever the credentials you connect allow inside FullStory. If FullStory lets you scope a key to specific permissions, create a scoped one so the agent can only do what you intend. You can revoke the key inside FullStory at any time.

Yes. Composio supports multiple connected accounts for the same app, and that works in Claude, ChatGPT, or any other assistant you connect through Composio. Give each FullStory connection a name such as work or personal, and the assistant uses the one you mention in the request. Each account keeps its own credentials and nothing is merged.

The connection stops working the moment FullStory rejects the old key. Create a new key in FullStory and reconnect the account from the Composio dashboard or by asking your agent to reconnect FullStory. Nothing else changes.

Composio's free Hobby plan includes 100,000 tool calls per month with no credit card, which covers most personal FullStory use. Paid plans add higher limits and team features. Your FullStory plan and its API limits still apply as usual.

Built-in connectors usually give one AI access to a limited set of apps. Many people use Composio because it lets their AI connect to more apps than it normally supports, or connect to multiple accounts for the same app (e.g. connect Claude to multiple FullStory accounts).

With Composio, you connect FullStory once and then use it across different AI assistants without setting it up separately in each one. Connect your apps to Composio once, then connect Composio to whichever AI you use, whether that's Claude, ChatGPT, Hermes, or your own custom assistant.

Start with FullStory.It takes 30 seconds.

Managed auth, hosted MCP servers, and every FullStory tool your agent needs.Free to start.

Start building