Skip to content

Analytics

Heap MCP connector

Connect Heap to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot 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
  • Connects with an API key
  • Free 14-day trial
  • No credit card
ChatGPT Elaichi connected

Record a trial started event for user 48213 in Heap

Working in Heap with Elaichi

  • Get single Heap user deletion by ID
  • Create a Heap event
  • Update a Heap identity by ID
Ask anything…
Governance / Audit log Last 24 hours
Heap Update a Heap identity by ID Emily Carter · ChatGPT · 9:41 AM Done
Heap Create a Heap event Emily Carter · ChatGPT · 9:41 AM Done
Heap Get single Heap user deletion by ID Emily Carter · ChatGPT · 9:41 AM Done
Heap Update a Heap user by ID Megan Brooks · Claude · 9:38 AM Done
Heap Update a Heap account by ID Ryan Hayes · Cursor · 9:35 AM Done

How to connect Heap to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Heap MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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 Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

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

    Start Claude Code and run /mcp.

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

Heap MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

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

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

Heap MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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.

Heap MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

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

    Create a new connection, sign in and approve, then press Add to agent.

  4. 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 Heap to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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

What teams do with Heap through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Heap is logged.

  • 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 →

What connecting Heap gets you

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

Elaichi Agent

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, Cursor or Microsoft Copilot

The agent

Update Heap users and accounts by asking.

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

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

 • Connected 4 minutes ago
Cursor
M

Megan Brooks

 • Connected 2 hours ago
ChatGPT
R

Ryan Hayes

 • Connected Yesterday

AI apps

One Heap endpoint for every AI client.

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

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.

Tool catalog

All 7 Heap tools, no code to write.

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

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

Toolboxes

Each team gets its own Heap toolbox.

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

ElaichiConnections
Connection Scope Status Access
HE

Heap (Product)

Connected by Emily Carter

 Personal • Active 1 team · 6 members
HE

Heap (Growth)

Connected by Jake Morgan

 Organization • Active 3 teams · 24 members
HE

Heap (Customer Success)

Connected by Megan Brooks

 Organization • Active 2 teams · 11 members
HE

Heap (Privacy)

Connected by Tyler Reed

 Personal • Needs re-auth 1 team · 3 members
HE

Heap (Data Platform)

Connected by Ryan Hayes

 Personal • Active Not shared
HE

Heap (Marketing)

Connected by Ashley Parker

 Personal • Active 2 teams · 9 members

Shared connections

Share the Heap connection, never the key.

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

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM
E

Emily Carter

[email protected]

 Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM
J

Jake Morgan

[email protected]

 Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM
M

Megan Brooks

[email protected]

 Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM
T

Tyler Reed

[email protected]

 Heap Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM
R

Ryan Hayes

[email protected]

 Heap Events Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM
A

Ashley Parker

[email protected]

 Heap Events List Toolbox

Audit log

Every Heap change names who made it.

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

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.

Heap digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch events

    Heap

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s

  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve

  6. Post the digest

    Heap

    Queued

Workflows

A schedule runs Heap work end to end.

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

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%

Collections and dashboards

Heap health numbers, computed without a model.

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

For IT and engineering

Elaichi vs Zapier MCP vs Composio for Heap

All three can connect Heap to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Heap, by what to check
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 Heap tools Allow or restrict single Heap 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 Heap 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.

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.

More from the catalog

Browse all 650+ connectors →

Questions, answered

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, Microsoft Copilot, 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 role. Each person signs into Elaichi as themselves, and Elaichi never grants more than the Heap key already permits.

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.

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 restricting user deletion requests, for example. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.

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, Microsoft Copilot 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, 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 Heap?

Yes. Both let Claude, ChatGPT or Cursor use Heap. 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 Heap call.

How is Elaichi different from Composio for Heap?

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 Heap: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Heap in front of your team

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

Connect Heap Talk to us

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