How do I get an API Key for FullStory?

Log in to FullStory, navigate to Settings > API Keys, and click on 'Create Key' to generate a new token with Admin or Architect permissions.

What is the difference between ID and UID?

The 'id' is a system-generated unique identifier from FullStory, while the 'uid' is your application's own internal user ID passed via FS.identify.

Can I watch session playbacks through the agent?

The agent can retrieve the 'fsUrl' for any session, which is a direct link to watch the playback in your browser. You cannot watch the video inside the chat interface directly.

Are custom user properties supported?

Yes! When you use 'upsert_user' or 'get_user_details', all custom properties stored in the 'properties' object are accessible and manageable via the agent.

FullStory MCP Server for Cursor 11 tools — connect in under 2 minutes

Name: FullStory
Availability: InStock
Author: Vinkius

docs.cursor.com/context/model-context-protocol

Built by Vinkius GDPR 11 Tools IDE

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install FullStory and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "fullstory": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About FullStory MCP Server

Connect your FullStory account to any AI agent to automate your digital experience intelligence (DXI) and product analytics workflows through the Model Context Protocol (MCP). FullStory provides a comprehensive view of how users interact with your site or app. This MCP server enables you to manage user profiles, track server-side events, and retrieve session metadata and playback links directly through natural conversation.

Cursor's Agent mode turns FullStory into an in-editor superpower. Ask Cursor to generate code using live data from FullStory and it fetches, processes, and writes — all in a single agentic loop. 11 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

Key Features

User Lifecycle Management — List all captured users, fetch detailed profile metadata, and upsert records to maintain accurate identity mapping.
Session Oversight — Retrieve a list of recording sessions for specific users and access playback URLs to visualize the customer journey.
Interaction Events — Fetch the complete set of captured events (clicks, navigations, custom events) for any specific session ID.
Server-Side Tracking — Log custom interaction events programmatically from your backend to enrich your FullStory datasets.
Segment Discovery — Access and list configured user segments to understand high-level audience behavior.
Data Exports — Monitor and list generated raw data bundles for deeper analytical processing.
Privacy Compliance — Programmatically delete user data to support GDPR and CCPA requests via simple AI commands.

The FullStory MCP Server exposes 11 tools through the Vinkius. Connect it to Cursor in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect FullStory to Cursor via MCP

Follow these steps to integrate the FullStory MCP Server with Cursor.

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"

Add the server config

Paste the JSON configuration above into the mcp.json file that opens

Save the file

Cursor will automatically detect the new MCP server

Start using FullStory

Open Agent mode in chat and ask: "Using FullStory, help me..." — 11 tools available

Why Use Cursor with the FullStory MCP Server

Cursor AI Code Editor provides unique advantages when paired with FullStory through the Model Context Protocol.

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

Cursor's Composer feature can generate entire files using real-time data fetched through MCP — no copy-pasting from external dashboards

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

FullStory + Cursor Use Cases

Practical scenarios where Cursor combined with the FullStory MCP Server delivers measurable value.

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

FullStory MCP Tools for Cursor (11)

These 11 tools become available when you connect FullStory to Cursor via MCP:

create_event

Automatically mapped for server-side metrics injection that bypassed the frontal JavaScript client. Dispatch a custom backend event into FullStory

create_update_user

Used to synchronize custom tenant data into the FullStory analytics boundary for enhanced session context. Upsert a user identity into FullStory tracking

delete_user

Permanently removes privacy-sensitive telemetry, custom property links, and session aggregations inside FullStory. Erase a user profile and their associated session history

get_account_info

Validates live integration capability and fetches workspace scope definitions. Verify authentication and retrieve basic platform stats

get_session

Resolves page transitions, total active time, event markers, and active direct access tracking links. Retrieve deep metadata for a specific session recording

get_session_events

Exposes click trails, navigation mutations, error logs, and precise structural DOM changes. Fetch the chronological telemetry events for a session

get_user

Retrieves raw session metadata, total session durations, custom variables, and cross-device interaction boundaries. Get full tracking profile and behavior history for a specific user

list_exports

Resolves the status of bulk data offloads, processing states, and download URIs for warehouse ingestion. List raw data export jobs available for download

list_segments

Resolves saved audience definitions, population counts across the last 30 days, and logical filter structures. List dynamic audience segments built in FullStory

list_sessions

Resolves a subset of sessions matching provided JSON query criteria, exposing playback links, browser signatures, and metric overlays. List or search session recordings based on telemetry

list_users

Resolves user identities, custom parameters, session counts, and aggregate behavioral profiles across the analytics boundary. Query the FullStory subscriber and visitor directory for analytics

Example Prompts for FullStory in Cursor

Ready-to-use prompts you can give your Cursor agent to start working with FullStory immediately.

"List the last 5 sessions for user UID 'user_12345'."

"Show me the full profile details for FullStory ID '123:456'."

"Track a server event 'Subscription Renewed' for user 'johndoe@email.com'."

Troubleshooting FullStory MCP Server with Cursor

Common issues when connecting FullStory to Cursor through the Vinkius, and how to resolve them.

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

FullStory + Cursor FAQ

Common questions about integrating FullStory MCP Server with Cursor.

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design — tool calls require user visibility and approval.

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.