How to Use the FullStory MCP in Cline

Q: How does Cline fetch FullStory session recordings?

Cline calls getsession using the session ID to retrieve metadata and playback links. It reads this data to understand the user's journey and find where things went wrong.

Q: Can Cline write code based on FullStory events?

Yes, Cline uses getsessionevents to analyze DOM changes and JavaScript errors. It then edits your local files to fix the underlying codebase issues.

Q: How do I sync customer data using FullStory and Cline?

You can ask Cline to write a sync script that calls createupdateuser. Cline will generate the code, link it to your database, and run tests to verify the integration.

Let Cline write code, run tests, and fix frontend bugs by analyzing live FullStory session recordings in VS Code.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect FullStory MCP to Cline

Create your Vinkius account to connect FullStory to Cline and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup FullStory with Cline

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Resolve UI issues autonomously using Cline

This MCP Server uses `get_session` and `get_session_events` to let Cline fetch raw telemetry directly into VS Code. When you give Cline a bug report, it retrieves the user's exact path, inspects the DOM mutations, and starts editing your code. Cline doesn't just show you the issue; it writes the patch, runs your test suite, and verifies the fix. You get a complete resolution cycle driven entirely by actual user behavior data.

Inject server-side tracking via Cline

The tool employs `create_event` to insert custom backend events into your tracking pipeline. Cline analyzes your backend routes, writes the event tracking code, and ensures it bypasses client-side ad blockers. It handles the entire integration cycle from writing the API call to verifying that the event payload matches your schema. This ensures your analytics remain accurate without tedious manual coding.

Query visitor records inside your IDE

This MCP Server uses `list_users` and `get_user` to pull behavioral profiles directly into Cline's active context. You can ask Cline to cross-reference a user's session history with your database records to see where they got stuck. It maps custom variables and session counts directly to your workspace files. Cline uses this context to suggest layout improvements or fix broken flows based on real usage patterns.

Setup guide

Set up FullStory MCP in Cline

Prerequisites

VS Code with Cline extension installed
Active Vinkius subscription with a valid endpoint token

1

Open Cline MCP settings

Click the Cline icon in the VS Code sidebar to open the Cline panel. Then click the MCP Servers icon (server stack) at the top-right corner of the panel.
2

Add a remote server

Click "Remote Servers" at the top, then click "Add Remote MCP". In the Name field, type fullstory-mcp. In the URL field, paste your Vinkius endpoint: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp. Get your token from cloud.vinkius.com.
3

Enable the server

After saving, the server appears in the Cline MCP panel. Toggle the switch to enable it. The status indicator turns green when the connection is live.
4

Start using tools

Return to the Cline chat and ask: "Check my latest FullStory refund status." Cline will discover the available tools and request your approval before invoking each one — giving you full control over every action.

Cline MCP Settings

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

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by FullStory. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect FullStory now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about FullStory MCP in Cline

Cline calls `get_session` using the session ID to retrieve metadata and playback links. It reads this data to understand the user's journey and find where things went wrong.

Yes, Cline uses `get_session_events` to analyze DOM changes and JavaScript errors. It then edits your local files to fix the underlying codebase issues.

You can ask Cline to write a sync script that calls `create_update_user`. Cline will generate the code, link it to your database, and run tests to verify the integration.

Click the MCP icon in the Cline sidebar, then add the server using the configuration panel or edit `cline_mcp_settings.json` directly.

The MCP server retrieves visitor records and behavioral profiles. To protect privacy, ensure your API key has restricted scopes and that your codebase masks sensitive fields before syncing.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript