Skip to content

Pendo MCP connector

The Pendo connector brings Pendo's visitors, accounts, segments, and product usage into Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent, so each person can ask about feature adoption and engagement as themselves, with every call logged.

  • Connects over OAuth
  • Free 14-day trial
  • No credit card

Regions: US, US1, EU, Australia and Japan. Elaichi supports all of them; you pick your region when you connect.

ChatGPT Elaichi connected

Which accounts dropped in usage over the last 30 days?

Working in Pendo with Elaichi

  • List all applications
  • Search entities
  • Segment list
Ask anything…
Governance / Audit log Last 24 hours
Pendo Segment list Emily Carter · ChatGPT · 9:41 AM Done
Pendo Search entities Emily Carter · ChatGPT · 9:41 AM Done
Pendo List all applications Emily Carter · ChatGPT · 9:41 AM Done
Pendo Get entity Megan Brooks · Claude · 9:38 AM Done
Pendo List custom objects Ryan Hayes · Cursor · 9:35 AM Done

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

Step by step, for each AI app

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

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

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

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

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

What teams do with Pendo through Elaichi

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

  • Product

    See which features an account actually uses

    Before a roadmap review, pull usage for a product area in Pendo and see which accounts and visitors are active in it and which have gone quiet.

  • Customer Success

    Spot accounts whose usage is dropping

    Ask for a renewal account's app usage over the last 30 days next to the quarter before, and read its product engagement score alongside it.

  • Support

    See what a visitor did before a ticket

    Look up a visitor's recent activity across pages and features in Pendo so the reply speaks to what they were trying to do.

  • Marketing

    Build a segment for a launch

    Describe the audience in plain words, such as enterprise accounts that have not touched reporting, and have the segment created in Pendo ready for a guide or an email.

  • Sales

    Walk into a demo knowing the account

    Pull an account's metadata and engagement score from Pendo so the conversation starts from what the customer already uses.

  • Analytics

    Answer a usage question without a dashboard

    Ask how many visitors used a feature each week across every application in Pendo and get the time series summarized in the chat.

Try asking

  • “Which accounts dropped in usage over the last 30 days?”
  • “Build a segment of visitors who have not used reporting.”
  • “Show me the product engagement score for Acme Corp.”

See all 87 Pendo tools →

What connecting Pendo gets you

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

Elaichi Agent

Ask Elaichi to work across your apps.

Which accounts dropped in usage over the last 30 days?

Build a segment of visitors who have not used reporting.

Show me the product engagement score for Acme Corp.

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask Pendo a question, get a live answer.

Type a question about visitors, accounts, or feature usage and the agent answers from Pendo.

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 endpoint brings Pendo to every client.

Claude, ChatGPT, Cursor, Microsoft Copilot, and Microsoft Copilot reach Pendo through one governed org endpoint, with no shared API key.

ElaichiTools
Tool Action Description
List all applications List Retrieve a list of subscriptions and applications you have access to. Often used as a first step with other tools (for example, passing App IDs to aggregateEntityUsage for usage data). Also confirms which application data you have access to through authentication.
Search entities Search Find Pendo items by name or conceptual meaning, including Pages, Features, Track Events, accounts, and saved clips. (Deprecated for guides and product areas).
Segment list List List all publicly shared segments with their names and IDs.
Get entity Get Retrieve the full configuration of a single Page, Feature, Track Event, or guide by its exact ID. Returns URL rules for Pages, element rules and Page context for Features, event rules for Track Events, and ordered steps, polls, and interactive elements for guides. Doesn't…
List custom objects List List the custom event properties designated as business objects. Returns each object's underlying field and kind, customer-facing display name and description when configured, and the date it was promoted to an object.

Tool catalog

87 Pendo tools, with no code to write.

Segments, visitors, accounts, product areas, and usage reports are covered out of the box.

ElaichiToolboxes
Name Source template Tools Created

Product toolbox

Pendo · product areas and feature usage

Pendo starter 18 Mar 4, 2026

Customer Success toolbox

Pendo · account health and engagement scores

— 9 Mar 2, 2026

Support toolbox

Pendo · visitor activity

— 24 Feb 27, 2026

Marketing toolbox

Pendo · segments for guides and campaigns

Pendo starter 6 Feb 19, 2026

Sales toolbox

Pendo · account usage before calls

— 31 Jan 30, 2026

Analytics toolbox

Pendo · usage time series and reports

— 12 Jan 22, 2026

Toolboxes

Each team gets its own Pendo toolbox.

Product keeps segments and usage, Support keeps visitor activity, and nobody sees more.

ElaichiConnections
Connection Scope Status Access
PE

Pendo (Product)

Connected by Emily Carter

Personal • Active 1 team · 6 members
PE

Pendo (Customer Success)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
PE

Pendo (Support)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
PE

Pendo (Marketing)

Connected by Tyler Reed

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

Pendo (Sales EMEA)

Connected by Ryan Hayes

Personal • Active Not shared
PE

Pendo (Analytics)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Share a Pendo connection, not a credential.

Teammates work through the connected Pendo account without ever seeing a token.

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]

Pendo Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Pendo Visitors Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Pendo Visitors List Toolbox

Audit log

Every Pendo call names who made it.

When, who, what happened, and which segment or account, 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.

Pendo digest

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

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch visitors

    Pendo

    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

    Pendo

    Queued

Workflows

A schedule starts the Pendo digest itself.

Usage is fetched, grouped, drafted into a digest, approved by a person, then posted to Pendo.

Pendo health

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

Live

Visitors

1,284 ↓ 12%

Accounts

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Visitors created

Last 14 days

By team

Share of activity

Product 34%

Customer Success 27%

Support 21%

Marketing 18%

Collections and dashboards

Pendo health numbers, computed with no model.

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

Why connect Pendo's MCP server through Elaichi

Pendo builds and runs this MCP server. Elaichi sits in front of it, so Pendo's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Pendo's server directly, outside Elaichi, get none of this.

  • One address for every AI client

    Claude, ChatGPT, Cursor and Microsoft Copilot reach Pendo's tools at the same Elaichi address as every other connected app. Nobody adds Pendo's server to each client one by one.

  • Each person signs in as themselves

    Each person signs in to Elaichi as themselves. Members connect with their own Pendo sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.

  • Rules checked before a call leaves

    Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Pendo's server. By default, a tool Pendo does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.

  • One audit log for every app

    Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.

  • Tool issues go to Pendo

    Pendo builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Pendo team.

    support.pendo.io/hc/en-us

Why run a vendor's MCP server through Elaichi →

For IT and engineering

Elaichi vs Zapier MCP vs Composio for Pendo

All three can connect Pendo 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 Pendo, 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 Pendo tools Allow or restrict single Pendo 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 Pendo 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.

Pendo tools for your AI agents

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

Questions, answered

How do I connect Pendo to Claude?

Connect Pendo in Elaichi and sign in to Pendo when prompted, which is the whole setup on the Pendo side. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. There is no OAuth application to register in Pendo and no client ID or secret to generate.

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

Yes. Once Pendo 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 Pendo once and every client sees it.

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

It can look up visitors and accounts in Pendo, read their activity and engagement scores, report feature and app usage over time, list product areas, and create, update, or delete segments. Short, specific asks such as a visitor's activity this week or a segment of accounts on one plan work better than long requests.

Does connecting Pendo give the AI every application, segment, and account?

No. The AI works inside the Pendo access of the person who signed in, so it sees the applications, segments, and accounts that person can already see in Pendo. Elaichi can narrow that further with restrictions, and it never widens it.

Can my team share one Pendo connection?

Yes. One person connects Pendo in Elaichi and shares it with a team, and nobody else handles a credential. Each person still signs in to Elaichi as themselves, so the audit log names who asked for a Pendo segment or usage report.

Can I stop an agent from deleting or changing segments in Pendo?

Yes. Restrictions in Elaichi work per action, so you can allow reading Pendo usage and visitors while restricting segment creation, updates, or deletion. A restricted action still appears in Elaichi's tool search, flagged as restricted, but the AI client cannot run it, whatever the prompt says.

What happens to a Pendo connection when someone leaves?

Offboarding that person in Elaichi ends their access to Pendo through every client at once. A shared Pendo connection keeps working for everyone else on the team. If you want Pendo gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client.

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

Yes. Pendo 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 Pendo?

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

How is Elaichi different from Composio for Pendo?

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

Put Pendo 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