How to Use the Hotjar MCP in CrewAI

Q: Can I assign different Hotjar tools to different CrewAI agents?

Yes. When defining your MCPServerHTTP tool in CrewAI, you can use the toolfilter argument. This lets you give a 'Data' agent access to listfunnels while a 'UX' agent only gets getrecording, enforcing role specialization.

Q: How would a CrewAI team use Hotjar to find a bug?

A 'Monitor' agent would use listrecordings to scan for sessions with errors. It would pass the session ID to an 'Analyst' agent, which uses getrecording to watch it and identify the bug. Finally, a 'Reporter' agent would take the findings and create a ticket.

Deploy a CrewAI team to autonomously monitor user experience. Agents use Hotjar tools to find friction, analyze it, and report back.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Hotjar MCP to CrewAI

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Assemble a UX monitoring crew

One agent, the 'Scout', uses `list_recordings` to find sessions with rage clicks or errors. It passes those session IDs to a 'Behavioral Analyst' agent. The Analyst agent uses `get_recording` to review the session, summarizes the user's struggle, and then tasks a 'Scribe' agent with filing a detailed bug report. Each agent has a specific role, using the exact Hotjar tool it needs.

Deploy a conversion optimization team with this MCP Server

A 'Metrics' agent periodically calls `list_funnels` and `get_survey_stats`. If it detects a drop-off, it alerts the 'Strategist' agent. The Strategist then directs a 'Visualizer' agent to pull the corresponding `get_heatmap` and `list_recordings`. The team works together to find not just *what* is broken, but *why*, using the server to gather evidence.

Create an autonomous feedback crew

A 'Listener' agent constantly checks `list_feedback_responses` and `list_survey_responses` for new entries. It passes anything negative to a 'Triage' agent. The Triage agent uses `lookup_user` to get context on the user, then decides the next step. It might ask a 'Communicator' agent to draft a reply or escalate the issue to a human, all without manual intervention.

Setup guide

Set up Hotjar 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 Hotjar tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

task = Task(
    description="List recent Hotjar 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="Hotjar Analyst",
        goal="Access and analyze Hotjar data via MCP.",
        backstory="Expert analyst with direct Hotjar access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Hotjar 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 Hotjar. 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 Hotjar 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 Hotjar MCP in CrewAI

You just pass the Vinkius MCP URL to your Agent definition in CrewAI. The agent will automatically have access to all the Hotjar tools, like `list_recordings` and `get_heatmap`, to complete its tasks.

Yes. When defining your `MCPServerHTTP` tool in CrewAI, you can use the `tool_filter` argument. This lets you give a 'Data' agent access to `list_funnels` while a 'UX' agent only gets `get_recording`, enforcing role specialization.

A 'Monitor' agent would use `list_recordings` to scan for sessions with errors. It would pass the session ID to an 'Analyst' agent, which uses `get_recording` to watch it and identify the bug. Finally, a 'Reporter' agent would take the findings and create a ticket.

It lets you build a team of autonomous agents that can fully manage a process like UX monitoring. You don't just ask a question; you deploy a crew that continuously watches Hotjar and takes action.

Vinkius ensures that each tool call from your CrewAI agents, whether it's for `get_recording` or `lookup_user`, runs in a completely isolated, single-use environment. This ephemeral execution means sensitive user session data is processed and immediately discarded, never stored.

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