Pendo (US1) MCP connector
The Pendo (US1) connector brings your Pendo accounts, visitors, segments and product usage from the US1 region to Claude, ChatGPT, Cursor and any MCP client, so your team can ask about adoption and build segments in plain language.
-
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 (US1) to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Pendo (US1) once
-
Open Connections, choose Add connection, and pick Pendo (US1).
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Pendo (US1). Pendo (US1)'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 (US1) 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 (US1) 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 (US1) 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 (US1) 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 (US1) 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 really uses
Ask how a specific account used each product area over the last quarter and get the usage trend back as a plain answer. No dashboard to build first.
-
Customer Success
Check account activity before a renewal call
Pull an account's recent activity, its engagement score and the visitors who have gone quiet, then walk into the call knowing where adoption stands.
-
Support
Find what a visitor did before writing in
Look up the visitor who opened the ticket and see which parts of the product they touched and when, so the reply speaks to what actually happened.
-
Marketing
Build a segment for the next campaign
Describe the audience in words, such as accounts that adopted one feature but not another, and have the segment created in Pendo ready to use.
-
Leadership
Pull the product engagement score every Monday
Ask for the product engagement score and app usage across all applications, broken down by week, and get the numbers without waiting on an analyst.
-
Sales
Compare usage across target accounts
Before a quarterly review, line up usage for the accounts in a territory and see which ones are growing and which have stalled.
Try asking
- “Which accounts dropped in usage over the last 30 days?”
- “Build a segment of visitors who used Reports this month.”
- “Show the product engagement score for our enterprise accounts.”
Compare
Elaichi vs Zapier MCP vs Composio for Pendo (US1)
All three can connect Pendo (US1) 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 (US1) tools | Allow or restrict single Pendo (US1) 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 (US1) 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 (US1) tools for your AI agents
87 tools are ready to call through Elaichi's MCP endpoint the moment you connect Pendo (US1), governed by the same roles, restrictions, and audit log as everything else in Elaichi. Pendo (US1) builds and runs these tools.
No tools match your search.
See it in Elaichi
What connecting Pendo (US1) gets you
6 screens from the product, each doing one job for your Pendo (US1) account.
The agent
Ask Pendo (US1) which accounts went quiet.
Plain questions, answered from live visitors, accounts and segments in Pendo (US1).
- accounts
- visitors
- 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 used Reports this month.
Show the product engagement score for our enterprise accounts.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint brings Pendo (US1) to every client.
Claude, ChatGPT and Cursor reach Pendo (US1) usage through one governed endpoint, no shared API key.
Copy the endpoint
Tool catalog
87 Pendo (US1) tools, ready without code.
Accounts, visitors, segments, product areas and usage, covered with no custom code to write.
- List all applications
- Search entities
- Segment list
- Get entity
Toolboxes
Every team gets its own Pendo (US1) toolbox.
Product sees usage, Customer Success sees accounts, each team scoped to the work it does.
- Product
- Customer Success
- Support
- Marketing
Shared connections
Share Pendo (US1) without sharing a credential.
One person connects Pendo (US1), teams and members work through it, nobody sees a secret.
- Product
- Customer Success
- Support
- Marketing
Audit log
Every Pendo (US1) call is on the record.
Who read which account, built which segment, and when, in one 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 turns Pendo (US1) usage into action.
Accounts are fetched, grouped and drafted into a digest, approved by a person, posted back.
Pendo (US1) digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch accounts
Pendo (US1)
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 (US1)
Queued
Collections and dashboards
Pendo (US1) health, computed without a model.
Four metrics, 14 days of segments created, a breakdown by team, refreshed on schedule.
Pendo (US1) health
Refreshed 4 minutes ago · every 15 minutes · from the accounts collection
Accounts
1,284 ↓ 12%
Visitors
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Accounts 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 (US1) to Claude?
Two steps. In Elaichi, choose the Pendo (US1) connector and sign in to Pendo over OAuth, which is the ordinary Pendo login screen for the US1 region, with no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Pendo in US1 appears in Claude the next time you open it.
Does Pendo (US1) work with ChatGPT and Cursor as well as Claude?
Yes. Pendo in US1 is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, is pasted into Claude, ChatGPT, Cursor, any other MCP client, or used by the Elaichi Agent. There is nothing to set up separately for each client.
What can an AI agent actually do with my Pendo (US1) data?
With Pendo in US1 connected, an agent can look up accounts and visitors, read their activity and usage over time, compare product areas and applications, report the product engagement score, and create, update or delete segments. In practice that means asking which accounts dropped off last month or asking for a segment of visitors who tried a feature once. Short, concrete asks work better than long paragraphs.
Does connecting Pendo (US1) give the AI access to every account and visitor?
No. Access to Pendo in US1 follows the person who signed in, so the agent sees only the applications, accounts and visitors that person can already see in Pendo. Elaichi can narrow that further by role and restriction, and it can never widen it beyond what Pendo itself allows.
Can I stop an agent from deleting or changing segments in Pendo (US1)?
Yes. Restrictions in Elaichi work per action, so you can allow reading accounts and usage from Pendo in US1 while blocking the actions that create, update or delete segments. A restricted action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt can reach it.
What happens to a Pendo (US1) connection when someone leaves?
Offboarding the person in Elaichi ends their access to Pendo in US1 at once, across every client they used. If they shared a Pendo connection with a team, it keeps working for everyone else. Disconnecting Pendo (US1) once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.
Does the Pendo (US1) MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Pendo (US1) 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 (US1)?
Yes. Both let Claude, ChatGPT or Cursor use Pendo (US1). 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 (US1) call.
How is Elaichi different from Composio for Pendo (US1)?
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 (US1): 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 (US1) 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.