Hotjar
Heatmaps and session recordings.
Verdict
Common use cases
- Pull session replays for bug reports
- Analyze heatmap clicks before design reviews
- Retrieve survey responses during sprint planning
- Identify funnel drop-off points in real time
- Share user feedback excerpts with support team
Integration
- Vendor
- Hotjar
- Category
- developer-tools
- Auth
- OAUTH2
- Composio slug
hotjar
Tools
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Click 'Add Integration' and select Hotjar from the list. 3. You'll be redirected to Hotjar's OAuth consent screen — sign in with an account that has Admin or Owner permissions on the sites you want to query. 4. Grant read access to sites, recordings, heatmaps, surveys, and feedback widgets when prompted. 5. Hotjar will redirect you back to Switchy with a confirmation message. 6. Open any Space and type '@Hotjar list my sites' to verify the connection — you should see a list of your tracked domains. 7. If the response is empty or shows an error, revisit Integrations and reconnect, ensuring you selected the correct Hotjar organization during OAuth.
What teammates see: by default, memories from Hotjar are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List Tracked Sites
@Hotjar show me all sites currently being tracked in my accountOpen in a Space →
Recent Session Recordings
@Hotjar fetch the ten most recent session recordings from our homepage and summarize any unusual behaviorOpen in a Space →
Heatmap Summary
@Hotjar get the heatmap data for our pricing page from the last seven days and highlight the most-clicked elementsOpen in a Space →
Survey Responses
@Hotjar retrieve all responses from our post-checkout survey launched this month and group them by sentimentOpen in a Space →
Funnel Drop-Off Analysis
@Hotjar analyze the signup funnel for drop-off points and show me which step has the highest exit rateOpen in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@hotjar show me the top 5 pages with the highest rage-click rates from the last 7 days
Based on Hotjar session recordings from the past week, here are the pages with the most rage-click activity: 1) /checkout/payment (47 rage-click events, avg 3.2 clicks per session), 2) /account/settings (31 events), 3) /search/results (28 events), 4) /product/compare (19 events), 5) /support/contact (14 events). The payment page shows users repeatedly clicking the 'Submit Order' button, suggesting a loading state or validation issue isn't surfacing clearly.
This example assumes the MCP can query Hotjar's Recordings API and aggregate interaction data. Rage-click detection depends on Hotjar's tracking configuration and may require a Business plan. Results reflect only sessions where tracking was active and users consented to recording.
@hotjar create a new feedback survey asking users why they abandoned the cart, target it to the /checkout page
Survey created successfully. Title: 'Cart Abandonment Feedback'. Question: 'What stopped you from completing your purchase today?' (open text field). Targeting: Appears on /checkout/* after 10 seconds of inactivity. Survey ID: srv_8k3m9n2p. The survey is now live and will start collecting responses immediately. You can view results in your Hotjar dashboard under Feedback > Surveys.
This write action creates a live survey on your site. The MCP needs OAuth scopes for survey creation and site configuration. Survey appearance depends on your Hotjar plan tier and existing survey limits. Always preview targeting rules in Hotjar's dashboard before deploying to avoid interrupting critical user flows.
@hotjar analyze heatmap data for /pricing and tell me which CTA gets the most attention but lowest conversion
Heatmap analysis for /pricing (last 30 days, 4,821 sessions): The 'Start Free Trial' button in the hero section receives 68% of clicks in that area, but only 12% of those clicks convert to signups (tracking via /signup/confirm pageview). In contrast, the 'See Enterprise Plans' link lower on the page gets 19% of clicks but has a 41% conversion rate to demo requests. This suggests the free trial button attracts browsers, while the enterprise link draws higher-intent visitors.
This synthesis example pairs Hotjar's heatmap click data with conversion tracking. Accuracy depends on proper goal configuration in Hotjar and consistent URL structures. The MCP can't directly access your analytics platform, so conversion rates here assume Hotjar's funnel tracking is set up. Cross-reference with your primary analytics tool for validation.
Use-case deep-dives
When Hotjar MCP fits a lean product discovery cycle
A 5-person product team runs weekly discovery sessions where they review heatmaps and session recordings to validate feature hypotheses. The Hotjar MCP lets them pull heatmap snapshots and recording metadata directly into a Switchy thread without tab-switching to the Hotjar dashboard. This works if your team already uses Hotjar as the primary analytics layer and you're reviewing 10-20 recordings per week. If you're doing deeper funnel analysis or need to cross-reference with event data from Amplitude or Mixpanel, the MCP becomes a narrow window into one tool—you'll still need the full dashboard open. The OAuth2 flow means each team member authenticates once and shares access in the workspace. Best for teams where Hotjar is the single source of truth on user behavior, not a supplementary tool.
Hotjar MCP for customer support context gathering
A 3-person support team handles 40-60 tickets daily, many requiring session replay lookups to understand what the user actually did. The Hotjar MCP lets them search for recordings by user ID or URL and embed the replay link in the ticket thread without leaving Switchy. This shortens the median triage time when the issue is a UX confusion, not a bug. The trade-off: if your support flow already lives in Zendesk or Intercom and those tools have native Hotjar integrations, the MCP adds a layer you don't need. It wins when your team does ticket triage in Switchy and wants to avoid the Hotjar dashboard entirely. The OAuth2 setup is straightforward—one auth per user, no API key rotation. If you're triaging fewer than 10 tickets a week that need replay, the integration overhead isn't worth it.
When Hotjar MCP helps designers catch friction early
A designer and frontend engineer pair on a new checkout flow and want to spot usability issues before the feature ships to all users. The Hotjar MCP surfaces click rage events and dead clicks from the staging environment directly in their Switchy design review thread. This works if you've already instrumented Hotjar on staging and you're running QA cycles every sprint. If your team uses FullStory or LogRocket for session replay, the MCP duplicates functionality—you're better off consolidating on one tool. The value is in keeping the design critique and the behavioral data in the same workspace, so the engineer can fix the issue without a handoff. OAuth2 means the designer and engineer each authenticate once. Best for teams under 10 people where design and engineering share the same Switchy workspace and Hotjar is the agreed-upon replay tool.
Frequently asked
What does the Hotjar MCP do in Switchy?
It connects your Hotjar account so AI agents can query heatmap data, session recordings, and user feedback without leaving the workspace. You ask questions about visitor behavior in natural language, and the agent pulls insights directly from your Hotjar projects. No need to export CSVs or switch tabs to analyze user sessions.
Do I need admin access to connect Hotjar via OAuth?
Yes. Hotjar's OAuth flow requires you to authorize access at the organization level, which means only account owners or admins can complete the connection. If you're a viewer-only user in Hotjar, you won't be able to authenticate. Check your role in Hotjar's team settings before attempting to connect.
Can the Hotjar MCP create new surveys or change heatmap settings?
No. This integration is read-only. It lets agents retrieve existing data — session replays, feedback responses, heatmap stats — but it won't modify your Hotjar configuration. If you need to launch a survey or adjust tracking, you still do that in Hotjar's dashboard. The MCP is for analysis, not campaign management.
Why use this instead of just logging into Hotjar directly?
Speed and context. Instead of manually filtering sessions or exporting feedback to correlate with other data, you ask the agent a question and it pulls the answer across Hotjar and your other connected tools. If you're already analyzing support tickets or product metrics in Switchy, the MCP keeps everything in one thread.
Who on the team should connect the Hotjar MCP?
Whoever owns your Hotjar account and has admin rights. Once connected, any Switchy team member with access to the workspace can query the data through AI agents. You don't need separate Hotjar seats for everyone — the MCP acts as a shared read interface for the whole team.