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 VS Code Copilot 11 tools — connect in under 2 minutes

Name: FullStory
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 11 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

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.

GitHub Copilot Agent mode brings FullStory data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 11 tools — Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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 VS Code Copilot 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 VS Code Copilot via MCP

Follow these steps to integrate the FullStory MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using FullStory

Ask Copilot: "Using FullStory, help me..." — 11 tools available

Why Use VS Code Copilot with the FullStory MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with FullStory through the Model Context Protocol.

VS Code is used by over 70% of developers — adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

FullStory + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the FullStory MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

FullStory MCP Tools for VS Code Copilot (11)

These 11 tools become available when you connect FullStory to VS Code Copilot 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 VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot 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 VS Code Copilot

Common issues when connecting FullStory to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

FullStory + VS Code Copilot FAQ

Common questions about integrating FullStory MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.