Pendo (EU) MCP connector
Connect Pendo (EU) to Elaichi and ask Claude, ChatGPT, or Cursor about visitors, accounts, segments, and product usage, with every answer limited to what the person asking can already see in Pendo.
-
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 (EU) to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Pendo (EU) once
-
Open Connections, choose Add connection, and pick Pendo (EU).
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Pendo (EU). Pendo (EU)'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 (EU) 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 (EU) 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 (EU) 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 (EU) 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 (EU) through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Product
Check feature adoption after a launch
Ask how many visitors used the new product area this week compared with last, and get the usage trend without building a report in Pendo first.
-
Customer Success
Spot accounts going quiet before renewal
Pull the product engagement score and recent app usage for the accounts renewing next quarter, then rank the ones whose activity has fallen.
-
Marketing
Build a segment for an in-app campaign
Describe the audience in plain words, such as visitors in a given country who have not opened a feature in 30 days, and have the segment created in Pendo ready for a guide.
-
Support
See what a visitor did before the ticket
Look up the visitor from the ticket and read their recent activity in the application, so the first reply already knows which pages and features they touched.
-
Sales
Read account usage before an expansion call
Ask which product areas an account uses most and which it has never opened, and walk into the call knowing where the upsell conversation belongs.
-
Leadership
Compare application usage week over week
Ask for app usage across every connected application over the last 14 days, broken down by account, and get the numbers rather than a screenshot of a chart.
Try asking
- “Which accounts dropped in product engagement score this month?”
- “Build a segment of visitors active in onboarding this month”
- “Show app usage for the mobile app over the last 14 days”
Compare
Elaichi vs Zapier MCP vs Composio for Pendo (EU)
All three can connect Pendo (EU) 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 (EU) tools | Allow or restrict single Pendo (EU) 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 (EU) 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 (EU) tools for your AI agents
87 tools are ready to call through Elaichi's MCP endpoint the moment you connect Pendo (EU), governed by the same roles, restrictions, and audit log as everything else in Elaichi. Pendo (EU) builds and runs these tools.
No tools match your search.
See it in Elaichi
What connecting Pendo (EU) gets you
6 screens from the product, each doing one job for your Pendo (EU) account.
The agent
Ask about visitors and accounts in plain language.
Elaichi's agent answers from live Pendo (EU) records, no dashboard building required.
- visitors
- accounts
- segments
- product areas
Ask Elaichi to work across your apps.
Which accounts dropped in product engagement score this month?
Build a segment of visitors active in onboarding this month
Show app usage for the mobile app over the last 14 days
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint reaches Claude, ChatGPT and Cursor.
Connect Pendo (EU) once and every MCP client signs in over OAuth, no shared key.
Copy the endpoint
Tool catalog
87 Pendo (EU) tools, no code to write.
Segments, visitors, accounts, product areas and usage, all cataloged and ready without custom code.
- List all applications
- Search entities
- Segment list
- Get entity
Toolboxes
Every team gets its own Pendo toolbox.
Product sees usage, Success sees accounts, Marketing sees segments, each scoped to its team.
- Product
- Customer Success
- Marketing
- Support
Shared connections
Share one connection without sharing a credential.
One person connects Pendo (EU), teammates work through it and never see a token.
- Product
- Customer Success
- Marketing
- Support
Audit log
Every segment change has a name on it.
The log records who touched which visitor, account or segment in Pendo (EU), and when.
- 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 usage digest itself.
Accounts are fetched, grouped, drafted into a digest, approved by a person, then posted back.
Pendo (EU) digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch visitors
Pendo (EU)
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 (EU)
Queued
Collections and dashboards
Pendo (EU) health, computed without a model.
Four metrics, 14 days of segments created and a team breakdown, refreshed on a schedule.
Pendo (EU) 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%
Marketing 21%
Support 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Pendo (EU) to Claude?
Pick Pendo (EU) in Elaichi and sign in to your Pendo EU account over OAuth, the same login screen you already use, with no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and your Pendo visitors, accounts and segments are available in the chat.
Does Pendo (EU) work with ChatGPT and Cursor as well as Claude?
Yes. Pendo in EU is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent. There is nothing extra to set up for each client.
What can an AI agent actually do with my Pendo (EU) data?
Through Elaichi an agent can list applications, look up visitors and accounts, read their activity, check app usage and product engagement scores, and create, update or delete segments in Pendo in EU. Short concrete asks work best, such as which accounts dropped in engagement this month. It works with what is in Pendo today rather than a stale export.
Does connecting Pendo (EU) give the AI everything in my Pendo subscription?
No. The agent works inside the access of the person who signed in to Pendo in EU, so it sees the applications, visitors and accounts that person can already open. Elaichi can narrow that further, for example to reading usage without touching segments, but it never widens it beyond what Pendo itself allows.
Can I stop an agent from deleting or changing segments in Pendo (EU)?
Yes. In Elaichi you restrict actions one by one, so creating, updating or deleting segments in Pendo in EU can be switched off while reading visitors and usage stays on. A restricted action is never shown to Claude, ChatGPT or Cursor, so no prompt can reach it.
What happens to a Pendo (EU) connection when someone leaves?
Offboarding that person in Elaichi ends their access to Pendo in EU at once, in every client they used. A connection they shared keeps working for everyone else on the team. Disconnecting Pendo (EU) once in Elaichi removes it from every client at the same time.
Does the Pendo (EU) MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Pendo (EU) 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 (EU)?
Yes. Both let Claude, ChatGPT or Cursor use Pendo (EU). 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 (EU) call.
How is Elaichi different from Composio for Pendo (EU)?
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 (EU): 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 (EU) 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.