Pendo MCP connector
The Pendo connector brings Pendo's visitors, accounts, segments, and product usage into Claude, ChatGPT, Cursor, and the Elaichi Agent, so each person can ask about feature adoption and engagement as themselves, with every call logged.
-
How it connects. Connects over OAuth. 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.
How to connect
How to connect Pendo to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Pendo once
-
Open Connections, choose Add connection, and pick Pendo.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Pendo. Pendo's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
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.
Pendo 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.
Pendo 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.
Pendo 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 Pendo 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.
Use cases
What teams do with Pendo through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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.”
Compare
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.
| 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 | $15 per user per month. | 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.
AI tools
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.
No tools match your search.
See it in Elaichi
What connecting Pendo gets you
6 screens from the product, each doing one job for your Pendo account.
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.
- visitors
- accounts
- segments
- product areas
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 or Cursor
MCP clients
One endpoint brings Pendo to every client.
Claude, ChatGPT, and Cursor reach Pendo through one governed org endpoint, with no shared API key.
Copy the endpoint
Tool catalog
87 Pendo tools, with no code to write.
Segments, visitors, accounts, product areas, and usage reports are covered out of the box.
- List all applications
- Search entities
- Segment list
- Get entity
Toolboxes
Each team gets its own Pendo toolbox.
Product keeps segments and usage, Support keeps visitor activity, and nobody sees more.
- Product
- Customer Success
- Support
- Marketing
Shared connections
Share a Pendo connection, not a credential.
Teammates work through the connected Pendo account without ever seeing a token.
- Product
- Customer Success
- Support
- Marketing
Audit log
Every Pendo call names who made it.
When, who, what happened, and which segment or account, in an append-only log.
- When
- Who
- What happened
- Type
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 starts the Pendo digest itself.
Usage is fetched, grouped, drafted into a digest, approved by a person, then posted to Pendo.
Pendo digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch visitors
Pendo
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
Pendo
Queued
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.
Pendo health
Refreshed 4 minutes ago · every 15 minutes · from the visitors collection
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%
Related connectors
More from the catalog
FAQ
Frequently asked questions
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, 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 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 blocking segment creation, updates, or deletion. A restricted action is never advertised to the AI client, so no prompt can reach it.
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, 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, 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 on Gold, no credit card. Connect it once and pick what each team can call.
- 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.