Bring Heatmaps
to CrewAI
Learn how to connect Hotjar to CrewAI and start using 15 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Hotjar MCP Server?
Connect your Hotjar account to any AI agent and access user experience analytics through natural conversation.
What you can do
- Survey Management — List all surveys, inspect questions and settings, retrieve individual responses, and review aggregate statistics (completion rate, NPS score, trends)
- Feedback Widgets — Browse incoming feedback widgets, inspect rating breakdowns, and review individual user submissions with screenshots
- Heatmaps — List all heatmap snapshots and inspect click, scroll, and move data for specific pages
- Session Recordings — Browse session recordings with duration and page count, and inspect metadata and events for individual sessions
- Conversion Funnels — List all funnels with step-by-step drop-off data for conversion optimization
- User Lookup — Retrieve session history and behavior data for a specific user ID
- Site Management — List all tracked sites configured in your Hotjar account
How it works
1. Subscribe to this server
2. Enter your Hotjar Client Secret from the API settings
3. Start analyzing user behavior from Claude, Cursor, or any MCP-compatible client
Who is this for?
- UX Researchers — review survey responses, analyze heatmap patterns, and watch session recordings to understand user behavior
- Product Managers — track conversion funnels, identify drop-off points, and monitor NPS scores
- Growth Teams — analyze feedback trends, optimize page engagement, and identify usability issues through AI
Built-in capabilities (15)
Verify connectivity
Get feedback widget details
Get heatmap details
Get recording details
Get survey details
Get survey statistics
List feedback widgets
List feedback responses
List funnels
List heatmaps
List recordings
List tracked sites
List survey responses
List surveys
Lookup user
Why CrewAI?
When paired with CrewAI, Hotjar becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Hotjar tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
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 Vinkius Edge URL directly in the
mcpsparameter 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
Hotjar in CrewAI
Hotjar and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Hotjar to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Hotjar in CrewAI
The Hotjar 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. All 15 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
Hotjar for CrewAI
Every tool call from CrewAI to the Hotjar MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I view survey responses and NPS scores?
Yes. Use list_surveys to see all surveys with response counts and status. Use get_survey_stats for aggregate metrics including completion rate, NPS score, and response trends. Use list_survey_responses to read individual user responses. Use get_survey for the full question list and settings.
Can I analyze heatmap data for specific pages?
Yes. Use list_heatmaps to browse all heatmap snapshots, then get_heatmap with a specific Heatmap ID to retrieve click, scroll, and move interaction data along with the page URL. This reveals where users focus attention and which elements they interact with most.
Can I track conversion funnel drop-offs?
Yes. The list_funnels tool retrieves all configured conversion funnels with step-by-step drop-off data. Each funnel shows the number of users entering each step and the percentage that continue to the next, helping you identify exactly where users abandon the flow.
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.
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
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.