Bring Heatmaps
to LangChain
Learn how to connect Hotjar to LangChain 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 LangChain?
LangChain's ecosystem of 500+ components combines seamlessly with Hotjar through native MCP adapters. Connect 15 tools via Vinkius and use ReAct agents, Plan-and-Execute strategies, or custom agent architectures. with LangSmith tracing giving full visibility into every tool call, latency, and token cost.
- —
The largest ecosystem of integrations, chains, and agents. combine Hotjar MCP tools with 500+ LangChain components
- —
Agent architecture supports ReAct, Plan-and-Execute, and custom strategies with full MCP tool access at every step
- —
LangSmith tracing gives you complete visibility into tool calls, latencies, and token usage for production debugging
- —
Memory and conversation persistence let agents maintain context across Hotjar queries for multi-turn workflows
Hotjar in LangChain
Hotjar and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Hotjar to LangChain 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 LangChain
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 LangChain 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 LangChain
Every tool call from LangChain 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 LangChain connect to MCP servers?
Use langchain-mcp-adapters to create an MCP client. LangChain discovers all tools and wraps them as native LangChain tools compatible with any agent type.
Which LangChain agent types work with MCP?
All agent types including ReAct, OpenAI Functions, and custom agents work with MCP tools. The tools appear as standard LangChain tools after the adapter wraps them.
Can I trace MCP tool calls in LangSmith?
Yes. All MCP tool invocations appear as traced steps in LangSmith, showing input parameters, response payloads, latency, and token usage.
MultiServerMCPClient not found
Install: pip install langchain-mcp-adapters