2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 11 Tools IDE

Cline is an autonomous AI coding agent inside VS Code that plans, executes, and iterates on tasks. Wire FullStory through the Vinkius and Cline gains direct access to every tool — from data retrieval to workflow automation — without leaving the terminal.

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.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "fullstory": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
FullStory
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.

Cline operates autonomously inside VS Code — it reads your codebase, plans a strategy, and executes multi-step tasks including FullStory tool calls without waiting for prompts between steps. Connect 11 tools through the Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.

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 Cline 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 Cline via MCP

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

01

Open Cline MCP Settings

Click the MCP Servers icon in the Cline sidebar panel

02

Add remote server

Click "Add MCP Server" and paste the configuration above

03

Enable the server

Toggle the server switch to ON

04

Start using FullStory

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

Why Use Cline with the FullStory MCP Server

Cline provides unique advantages when paired with FullStory through the Model Context Protocol.

01

Cline operates autonomously — it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts

02

Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window

03

Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation

04

Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing

FullStory + Cline Use Cases

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

01

Autonomous feature building: tell Cline to fetch data from FullStory and scaffold a complete module with types, handlers, and tests

02

Codebase refactoring: use FullStory tools to validate live data while Cline restructures your code to match updated schemas

03

Automated testing: Cline fetches real responses from FullStory and generates snapshot tests or mocks based on actual payloads

04

Incident response: query FullStory for real-time status and let Cline generate hotfix patches based on the findings

FullStory MCP Tools for Cline (11)

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

01

create_event

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

02

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

03

delete_user

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

04

get_account_info

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

05

get_session

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

06

get_session_events

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

07

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

08

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

09

list_segments

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

10

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

11

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 Cline

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

01

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

02

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

03

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

Troubleshooting FullStory MCP Server with Cline

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

01

Server shows error in sidebar

Click the server name to see logs. Verify the URL and token are correct.

FullStory + Cline FAQ

Common questions about integrating FullStory MCP Server with Cline.

01

How does Cline connect to MCP servers?

Cline reads MCP server configurations from its settings panel in VS Code. Add the server URL and Cline discovers all available tools on initialization.
02

Can Cline run MCP tools without approval?

By default, Cline asks for confirmation before executing tool calls. You can configure auto-approval rules for trusted servers in the settings.
03

Does Cline support multiple MCP servers at once?

Yes. Configure as many servers as needed. Cline can use tools from different servers within the same autonomous task execution.

Connect FullStory to Cline

Get your token, paste the configuration, and start using 11 tools in under 2 minutes. No API key management needed.