Hotjar MCP connector
The Hotjar connector brings your Hotjar surveys, survey responses and user lookups into Claude, ChatGPT, Cursor, Microsoft Copilot or any MCP client, so anyone on your team can ask what customers said and get an answer from live Hotjar records.
- App credentials
- Free 14-day trial
- No credit card
Summarize this week's responses to the onboarding survey
Working in Hotjar with Elaichi
-
List all Hotjar surveys
-
Get single Hotjar survey by ID
-
List all Hotjar survey responses
How to connect Hotjar to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Hotjar MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Hotjar MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Hotjar MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Hotjar MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Hotjar MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Hotjar to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Hotjar through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Hotjar is logged.
-
Product
Read this week's survey responses
Ask what people wrote in the onboarding survey since Monday and get the responses pulled straight from Hotjar, ready to summarize or sort into themes.
-
UX research
Compare two surveys side by side
Pull up the exit survey and the pricing page survey from Hotjar and ask how the answers differ, without exporting a spreadsheet first.
-
Marketing
Find out why visitors leave a page
Open the survey running on a landing page and ask for the most common reasons people gave for not signing up.
-
Support
Look up what one customer told you
Create a Hotjar user lookup for the person on the line and see which surveys they answered before you reply.
-
Customer success
Prepare for a renewal call
Before a check-in, ask for every Hotjar survey response from that account's users, so the call starts with what they actually said.
-
Leadership
Get a monthly voice of customer digest
Ask for all Hotjar surveys that collected responses this month and a short summary of what changed since last month.
Try asking
- “Summarize this week's responses to the onboarding survey”
- “Which Hotjar surveys collected responses in the last 30 days?”
- “Look up this customer's email and show the surveys they answered”
What connecting Hotjar gets you
6 screens from Elaichi, each doing one job for your Hotjar account.
Ask Elaichi to work across your apps.
Summarize this week's responses to the onboarding survey
Which Hotjar surveys collected responses in the last 30 days?
Look up this customer's email and show the surveys they answered
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask Hotjar what customers said, in plain words.
Type a question and the agent answers from live Hotjar surveys and responses.
Copy the endpoint
AI apps
One endpoint puts Hotjar in every client.
Claude, ChatGPT and Cursor reach Hotjar through one governed endpoint, no SDK, no shared key.
Tool catalog
4 Hotjar tools, no custom code to write.
Surveys, survey responses and user lookups are ready to use the moment Hotjar connects.
Toolboxes
Every team gets its own Hotjar toolbox.
Product reads survey responses, Support runs user lookups, each team sees only its toolbox.
Shared connections
Share Hotjar without ever sharing a credential.
One person connects Hotjar, teammates work through it, and nobody else sees the credentials.
Audit log
Know who read which Hotjar survey, and when.
Every call to Hotjar lands in an append-only log with who, what and which resource.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Hotjar digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch surveys
Hotjar
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Hotjar
Queued
Workflows
A schedule turns Hotjar responses into a digest.
Responses are fetched, grouped and drafted into a digest a person approves before it posts.
Hotjar health
Refreshed 4 minutes ago · every 15 minutes · from the surveys collection
Surveys
1,284 ↓ 12%
Survey responses
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Surveys created
Last 14 days
By team
Share of activity
Product 34%
UX research 27%
Marketing web 21%
Support 18%
Collections and dashboards
Hotjar survey numbers, computed without a model.
Four metrics, 14 days of responses and a team breakdown, refreshed on a schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Hotjar
All three can connect Hotjar to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Hotjar tools | Allow or restrict single Hotjar tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Hotjar call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Hotjar tools for your AI agents
4 tools are ready to call through Elaichi's MCP endpoint the moment you connect Hotjar, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Hotjar to Claude?
Connect Hotjar in Elaichi first: open the Hotjar connector, paste the app credentials from your Hotjar account, and the connection is live. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and your Hotjar surveys are ready to ask about.
Does Hotjar work with ChatGPT and Cursor as well as Claude?
Yes. Once Hotjar is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Hotjar once and every client you use picks it up.
What can an AI agent actually do with my Hotjar data?
With Hotjar connected, an agent can list your surveys, open one survey in detail, read through its responses, and run a user lookup for a specific person. In practice that means asking things like "what did people say in the checkout survey this week" or "which surveys has this customer answered" and getting an answer from live Hotjar records. Short, concrete asks like these work better than long sentences.
Does connecting Hotjar give the AI every survey in the account?
No. Every call to Hotjar through Elaichi runs as the person who signed in, so an agent sees the Hotjar surveys and responses that person can already see and nothing more. Elaichi can narrow that access further by role or for one person, and it never widens what Hotjar itself allows.
Can I stop an agent from creating or changing things in Hotjar?
Yes. In Elaichi you restrict actions one at a time, for a role or for one person, so you could allow reading Hotjar surveys and responses while restricting user lookups for most people. A restricted action still shows in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to a Hotjar connection when someone leaves?
Offboarding a person in Elaichi ends their access to Hotjar through every client at once. A Hotjar connection that was shared with a team keeps working for everyone else. If you ever want Hotjar gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.
Does the Hotjar MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Hotjar is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Hotjar?
Yes. Both let Claude, ChatGPT or Cursor use Hotjar. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Hotjar call.
How is Elaichi different from Composio for Hotjar?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Hotjar: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Hotjar in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot