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

Name: FullStory
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 11 Tools Framework

Connect your CrewAI agents to FullStory through the Vinkius — pass the Edge URL in the `mcps` parameter and every FullStory tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

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.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="FullStory Specialist",
    goal="Help users interact with FullStory effectively",
    backstory=(
        "You are an expert at leveraging FullStory tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token — get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in FullStory "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 11 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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.

When paired with CrewAI, FullStory becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call FullStory tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

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

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

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py — CrewAI auto-discovers 11 tools from FullStory

Why Use CrewAI with the FullStory MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with FullStory through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles — one agent researches, another analyzes, a third generates reports — each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

FullStory + CrewAI Use Cases

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

Automated multi-step research: a reconnaissance agent queries FullStory for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries FullStory, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain FullStory tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries FullStory against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

FullStory MCP Tools for CrewAI (11)

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

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

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

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

FullStory + CrewAI FAQ

Common questions about integrating FullStory MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.