Can my team share one Heap connection?

Yes. One person connects Heap, shares the connection with a team, and nobody else ever handles the Heap API key. Each teammate still signs into Elaichi as themselves, so every event recorded or account updated in Heap is logged under their own name.

Analytics

Heap MCP connector

Connect Heap to Elaichi and Claude, ChatGPT, Cursor and the Elaichi Agent can record events, update users, accounts and identities, and process deletion requests in Heap, with every call running as the signed-in person and logged.

Connect on Elaichi How to connect

How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
One address. https://api.elaichi.ai/mcp, the same for every user.
Their own access. An agent never gets more than the person it acts for.

7 tools

How to connect

How to connect Heap to Claude, ChatGPT or Cursor

Two steps, about a minute.

In Elaichi

Connect Heap once

Open Connections, choose Add connection, and pick Heap.
Optionally set Share with to give a team access, then press Connect.
Paste a Heap API key. One person generates a token in Heap and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

heap

All categories

Heap

Allium

Amplitude

Artie

Botify

DoiT

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

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

Heap 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 today. The plugin directory lives at chatgpt.com/plugins.

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

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

Connect Heap on Elaichi See pricing

Use cases

What teams do with Heap through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

Product

Record the event the product missed

When something happens outside the app, such as a signed contract or a support call, record it as an event in Heap so the funnel reflects what really happened.
Customer Success

Catch the user up after a check-in

After a call, update the Heap user with the new plan, health score or renewal date so the usage view matches what you just learned.
Marketing

Keep account properties clean for segments

Update industry, region or tier on a Heap account the moment it changes, so segments and reports stop drifting.
Sales

Stamp the closed deal onto the account

When a deal closes, write the plan and contract value onto the Heap account so product usage can be read against revenue.
Privacy

Handle a deletion request start to finish

Submit a user deletion in Heap when a request arrives, then check its status by ID before confirming back to the person who asked.
Data

Line up an identity after a change

When someone changes email or merges accounts, update the identity in Heap so their sessions sit under one person instead of two.

Try asking

“Record a trial started event for user 48213 in Heap”
“Update account 7710 in Heap with plan set to Enterprise”
“Check the status of the deletion request for user 91544”

See all 7 Heap tools below

AI tools

Heap tools for your AI agents

7 tools are ready to call through Elaichi's MCP endpoint the moment you connect Heap, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Heap gets you

6 screens from the product, each doing one job for your Heap account.

The agent

Update Heap users and accounts by asking.

Type what changed and the agent writes it to the right Heap user or account.

events
users
accounts
identities

Ask Elaichi to work across your apps.

Record a trial started event for user 48213 in Heap

Update account 7710 in Heap with plan set to Enterprise

Check the status of the deletion request for user 91544

Also runs in Claude, ChatGPT or Cursor

MCP clients

One Heap endpoint for every AI client.

Claude, ChatGPT and Cursor reach Heap through one governed endpoint, no SDK, no shared key.

ElaichiMCP clients

Claude

ChatGPT

Cursor

Copy the endpoint

https://api.elaichi.ai/mcp

Client	Connected by	Status	Last used
Claude	E Emma Laurent	• Connected	4 minutes ago
Cursor	S Sofia Ricci	• Connected	2 hours ago
ChatGPT	C Clara Nowak	• Connected	Yesterday

Tool catalog

All 7 Heap tools, no code to write.

Events, users, accounts, identities and deletion requests, ready the moment Heap is connected.

Create a Heap event
Update a Heap identity by ID
Update a Heap user by ID
Update a Heap account by ID

ElaichiTools

Tool	Action	Description
Create a Heap event	Create	Send a custom server-side event to Heap, such as backend order/transaction info or events not capturable client-side. Returns an empty JSON object on success. Requires app_id and event; you must supply either identity or user_id, but not both.
Update a Heap identity by ID	Update	Identify a Heap user by mapping an anonymous SDK user_id to a known identity such as an email, migrating all associated events to that identity. Returns an empty JSON object on success. Requires app_id, user_id, and identity. Heap allows only 1 identity per user_id and at most 10 user_ids per identity in a one-month window; extra calls are ignored.
Update a Heap user by ID	Update	Attach custom key-value properties to an identified Heap user from your servers; unknown identities are created as new users and existing properties are overwritten by name. Returns an empty JSON object on success. Required: app_id, identity.
Update a Heap account by ID	Update	Attach or update custom account properties for one or more accounts in Heap. Returns a plain-text 'OK' success acknowledgment with no structured body. Required: app_id, plus either account_id and properties (single-account update) or accounts (bulk update).
Create a Heap auth	Create	Create a temporary Heap auth token by exchanging API credentials via HTTP Basic Authentication. Returns: access_token.

Toolboxes

Each team gets its own Heap toolbox.

Product records events, Privacy handles deletions, each team sees only the toolbox scoped to it.

Product
Marketing
Customer Success
Sales

ElaichiToolboxes

Name	Source template	Tools	Created
Product toolbox Heap · events and user properties	Heap starter	18	Mar 4, 2026
Marketing toolbox Heap · account segments and properties	—	9	Mar 2, 2026
Customer Success toolbox Heap · user and account updates	—	24	Feb 27, 2026
Sales toolbox Heap · account plan and tier	Heap starter	6	Feb 19, 2026
Privacy toolbox Heap · user deletion requests	—	31	Jan 30, 2026
Data toolbox Heap · identities and event tracking	—	12	Jan 22, 2026

Shared connections

Share the Heap connection, never the key.

One person connects Heap once and teammates work through it without seeing the API key.

Product
Growth
Customer Success
Privacy

ElaichiConnections

Connection	Scope	Status	Access
HE Heap (Product) Connected by Emma Laurent	Personal	• Active	1 team · 6 members
HE Heap (Growth) Connected by James Whitfield	Organization	• Active	3 teams · 24 members
HE Heap (Customer Success) Connected by Sofia Ricci	Organization	• Active	2 teams · 11 members
HE Heap (Privacy) Connected by Daniel Ortega	Personal	• Needs re-auth	1 team · 3 members
HE Heap (Data Platform) Connected by Clara Nowak	Personal	• Active	Not shared
HE Heap (Marketing) Connected by Michael Brennan	Personal	• Active	2 teams · 9 members

Audit log

Every Heap change names who made it.

When, who, what happened and which user or account, kept in an append-only log.

When
Who
What happened
Type

ElaichiAudit log

When	Who	What happened	Type
2 minutes ago Mar 6, 2026, 3:10 PM	E Emma Laurent [email protected]	Restriction Created	Access
8 minutes ago Mar 6, 2026, 3:04 PM	J James Whitfield [email protected]	Restriction Updated	Access
14 minutes ago Mar 6, 2026, 2:58 PM	S Sofia Ricci [email protected]	Role Assigned	Access
20 minutes ago Mar 6, 2026, 2:52 PM	D Daniel Ortega [email protected]	Heap Users Updated	MCP
26 minutes ago Mar 6, 2026, 2:46 PM	C Clara Nowak [email protected]	Heap Events Created	MCP
32 minutes ago Mar 6, 2026, 2:40 PM	M Michael Brennan [email protected]	Heap Events List	Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule runs Heap work end to end.

Heap records are fetched, grouped and drafted into a digest, approved before posting back.

Heap digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

Run now

✓

Schedule

Every weekday at 08:00

0.2s
✓

Fetch events

Heap

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 Michael Brennan

Approve Deny
Post the digest

Heap

Queued

Collections and dashboards

Heap health numbers, computed without a model.

Four metrics, 14 days of events created and a team breakdown, refreshed on schedule.

Heap health

Refreshed 4 minutes ago · every 15 minutes · from the events collection

Live

Events

1,284 ↓ 12%

Users

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Events created

Last 14 days

By team

Share of activity

Product 34%

Growth 27%

Customer Success 21%

Privacy 18%

Related connectors

More from the catalog

Browse all 450+ connectors →

FAQ

Frequently asked questions

How do I connect Heap to Claude?

Two steps. Connect Heap in Elaichi by pasting in a Heap API key, there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude can then record events and update users and accounts in Heap as you.

Does Heap work with ChatGPT and Cursor as well as Claude?

Yes. Heap is connected once in Elaichi and the same endpoint, https://api.elaichi.ai/mcp, is added to Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. Nothing is set up per client.

What can an AI agent actually do with my Heap data?

With Heap connected, an agent can record an event, update a user, an account or an identity by ID, submit a user deletion request and check the status of one. Short concrete asks work best, such as setting a plan on account 7710 rather than a long paragraph. Reading reports and charts out of Heap is not part of this connector.

Does connecting Heap give the AI my whole workspace?

No. The Heap connection can only do what the API key it was connected with allows, and Elaichi can narrow that further to a handful of actions for a given team. Each person signs into Elaichi as themselves, and Elaichi never grants more than the Heap key already permits.

Can I stop an agent from deleting or changing things in Heap?

Yes. Restrictions in Elaichi work per action, so you can allow recording events in Heap while blocking user deletion requests, for example. A restricted action is never shown to Claude, ChatGPT or Cursor at all, so no prompt can reach it.

What happens to a Heap connection when someone leaves?

Offboarding a person in Elaichi ends their access to Heap at once, across every client they used. A shared Heap connection keeps working for everyone else on the team. Disconnecting Heap once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.

Does the Heap MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Heap 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, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Put Heap in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Connect Heap Talk to us

Works with: and any other MCP client, or the Elaichi Agent.
When the trial ends: Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.