# 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.

Source: https://elaichi.ai/connectors/hotjar/

## Facts

| | |
| --- | --- |
| Application | Hotjar |
| Category | Analytics |
| AI tools | 4 |
| Authentication | App credentials |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Hotjar is connected

- 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

## Connect Hotjar in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Hotjar.
2. Optionally set Share with, then press Connect.
3. Paste your Hotjar app credentials. Hotjar authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Hotjar tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Hotjar MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Hotjar MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

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.
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.

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

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Hotjar tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Hotjar through Elaichi

### Read this week's survey responses

Product. 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.

### Compare two surveys side by side

UX research. Pull up the exit survey and the pricing page survey from Hotjar and ask how the answers differ, without exporting a spreadsheet first.

### Find out why visitors leave a page

Marketing. Open the survey running on a landing page and ask for the most common reasons people gave for not signing up.

### Look up what one customer told you

Support. Create a Hotjar user lookup for the person on the line and see which surveys they answered before you reply.

### Prepare for a renewal call

Customer success. Before a check-in, ask for every Hotjar survey response from that account's users, so the call starts with what they actually said.

### Get a monthly voice of customer digest

Leadership. Ask for all Hotjar surveys that collected responses this month and a short summary of what changed since last month.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### 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 my team share one Hotjar connection?

Yes. One person connects Hotjar in Elaichi and shares the connection with a team, and nobody else ever handles the Hotjar app credentials. Each teammate still signs in as themselves, so the audit log names the actual person who read a survey or ran a user lookup.

### 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.

## All 4 Hotjar tools

Every tool below is callable through https://api.elaichi.ai/mcp once Hotjar is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Hotjar surveys** (List). List Hotjar surveys for a site. Returns survey objects with id, name, type, is_enabled, created_time, url, responses_url, questions, and sentiment_analysis_enabled. Required: site_id. Max 100 per page.
- **Get single Hotjar survey by ID** (Get). Get a single Hotjar survey for a site by id. Returns: id, url, created_time, updated_time, is_enabled, name, responses_url, type, questions, sentiment_analysis_enabled. Questions are always included. Required: site_id, id.
- **List all Hotjar survey responses** (List). List Hotjar survey responses for a survey, sorted newest first. Returns: id, answers, browser, country, created_time, device, hotjar_user_id, is_complete, os, recording_url, response_origin_url, user_attributes, window_size. Required: site_id, survey_id.
- **Create a Hotjar user lookup** (Create). Perform a Hotjar user lookup for a data subject, optionally deleting all found data. Returns an empty 202 Accepted response on success. Required: organization_id. The body must include data_subject_email or data_subject_site_id_to_user_id_map; with delete_all_hits false, a report-link email is sent to the data subject instead of deleting.
