How to Use the FullStory MCP in CrewAI

Deploy a team of autonomous CrewAI agents to investigate bugs and manage FullStory user telemetry.

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 CrewAI

Create your Vinkius account to connect FullStory to CrewAI 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 CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Investigate Bugs with CrewAI

The `list_sessions` tool exposes playback links and metric overlays matching your query criteria. The MCP Server processes this request while your researcher agent monitors new bug reports. It hands the session ID off to the next agent in the hierarchy. An analyst agent then calls `get_session_events` to rip through the click trails and error logs. The crew works autonomously to pinpoint the structural DOM changes that caused the crash. By the time engineering logs in, the root cause is already documented.

Map Behavioral Profiles

The `list_segments` tool resolves dynamic audience definitions and logical filter structures. Your data agent pulls the population counts for the last 30 days. It analyzes the raw numbers and passes the context to a reporting agent. That reporting agent uses `list_users` to query the visitor directory for specific custom parameters. The crew aggregates the behavioral profiles across the analytics boundary. You get a complete picture of user friction without writing a single database query.

Synchronize Analytics Metadata

The `create_update_user` tool synchronizes custom tenant data into the tracking profile. Your MCP Server handles the backend communication while a background agent watches your CRM. Your session context stays perfectly aligned with your source of truth. When backend processes finish, a separate agent fires `create_event` to inject server-side metrics. This bypasses the frontal JavaScript client completely. The crew maintains accurate telemetry records while your human engineers focus on shipping features.

Setup guide

Set up FullStory MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke FullStory tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="FullStory Analyst",
    goal="Access and analyze FullStory data via MCP.",
    backstory="Expert analyst with direct FullStory access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent FullStory transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

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

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="FullStory Analyst",
        goal="Access and analyze FullStory data via MCP.",
        backstory="Expert analyst with direct FullStory access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent FullStory transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

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

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 CrewAI

Pass the server URL directly into the mcps array of your Agent definition. For more granular control, import MCPServerHTTP and use a tool_filter. This lets you restrict specific agents to specific operations.

Yes. The framework maintains shared memory across the crew. A monitor agent can pull a session ID and pass it to an analyst agent for deeper inspection.

You can configure stdio, SSE, or Streamable HTTP. Most cloud deployments use HTTP for reliable, long-running agent operations.

Use the tool filter to block access to operations like delete_user. Only assign read-only capabilities to your standard research agents. Create a dedicated, highly restricted agent for deletion tasks.

Agents retrieve raw session metadata and cross-device boundaries via get_user. Vinkius handles the authorization layer through a single endpoint token. The integration operates strictly within a zero-trust architecture.

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