Pendo (Australia) MCP connector
The Pendo (Australia) connector brings visitors, accounts, segments and product usage from Pendo's Australia region to Claude, ChatGPT, Cursor and the Elaichi Agent, so each person can ask about adoption inside their own Pendo access.
-
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 (Australia) to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Pendo (Australia) once
-
Open Connections, choose Add connection, and pick Pendo (Australia).
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Pendo (Australia). Pendo (Australia)'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 (Australia) 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 (Australia) 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 (Australia) 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 (Australia) 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 (Australia) 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 a product area actually uses
Ask how often a feature was used over the last 30 days and which accounts drove it, pulled straight from Pendo in Australia.
-
Customer Success
Check an account's activity before a renewal call
Pull a customer's visitor activity and product engagement score so you walk into the call knowing who is active and who has gone quiet.
-
Marketing
Build a segment for the next campaign
Describe the audience in plain words, for example accounts in Australia that have not touched a feature, and have the segment created in Pendo.
-
Support
See what a visitor did before writing in
Look up a visitor's recent activity across product areas so you understand where they were before the ticket arrived.
-
Sales
Spot accounts whose usage is climbing
Compare app usage over time to find accounts whose adoption is rising fast enough to justify an expansion conversation.
-
Leadership
Get a weekly product engagement summary
Ask for engagement scores and usage trends across applications and product areas, summarized in a few lines without opening a dashboard.
Try asking
- “Which accounts in the Enterprise segment dropped in usage this month?”
- “Show me Acme's visitor activity for the last 30 days.”
- “Create a segment of accounts that never opened the Reports area.”
Compare
Elaichi vs Zapier MCP vs Composio for Pendo (Australia)
All three can connect Pendo (Australia) 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 (Australia) tools | Allow or restrict single Pendo (Australia) 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 (Australia) 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 (Australia) tools for your AI agents
87 tools are ready to call through Elaichi's MCP endpoint the moment you connect Pendo (Australia), governed by the same roles, restrictions, and audit log as everything else in Elaichi. Pendo (Australia) builds and runs these tools.
No tools match your search.
See it in Elaichi
What connecting Pendo (Australia) gets you
6 screens from the product, each doing one job for your Pendo (Australia) account.
The agent
Ask about adoption, get live Pendo answers.
Type a plain question and the agent answers from visitors, accounts and segments in Pendo (Australia).
- visitors
- accounts
- segments
- product areas
Ask Elaichi to work across your apps.
Which accounts in the Enterprise segment dropped in usage this month?
Show me Acme's visitor activity for the last 30 days.
Create a segment of accounts that never opened the Reports area.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint brings Pendo (Australia) to every client.
Claude, ChatGPT and Cursor connect over OAuth through one org endpoint, no SDK, no shared key.
Copy the endpoint
Tool catalog
87 Pendo (Australia) tools, ready without code.
Visitors, accounts, segments, product areas and usage reports, covered with no custom code to write.
- List all applications
- Search entities
- Segment list
- Get entity
Toolboxes
Each team gets its own Pendo toolbox.
Product sees usage, Marketing builds segments, Success checks accounts, each scoped to what their team needs.
- Product
- Customer Success
- Marketing
- Support
Shared connections
Share one Pendo (Australia) connection, keep the credential.
One person connects, teams and members work through it, and nobody else ever sees a credential.
- Product
- Customer Success
- Marketing
- Support
Audit log
Every Pendo (Australia) call is on the record.
See who read which segment or account, when, and from which client, 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 usage into a digest.
Usage is fetched, grouped, drafted into a digest, approved by a person, then posted to Pendo.
Pendo (Australia) digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch visitors
Pendo (Australia)
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 (Australia)
Queued
Collections and dashboards
Pendo (Australia) health, computed, never asked for.
Four metrics, 14 days of segments created, a team breakdown, refreshed on schedule, no model involved.
Pendo (Australia) 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 (Australia) to Claude?
In Elaichi, choose Pendo (Australia), and Pendo's own sign-in page opens for the Australia region, where you sign in with your usual Pendo account and approve access. There is 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. Claude signs you into Elaichi and Pendo in Australia is available.
Does Pendo (Australia) work with ChatGPT and Cursor as well as Claude?
Yes. Once Pendo (Australia) 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 in Australia once and every client picks it up.
What can an AI agent actually do with my Pendo (Australia) data?
With Pendo in Australia connected, an agent can look up a visitor's or account's recent activity, check feature usage across product areas and applications, pull a product engagement score, and list or build segments. It can also create, update or delete segments if you allow it. Short, specific asks like "show Acme's activity this month" work better than long paragraphs.
Does connecting Pendo (Australia) give the AI access to every account and segment in my subscription?
No. Every call to Pendo in Australia runs as the person who signed in, so the AI can only see the applications, accounts, visitors and segments that person could already see in Pendo. Elaichi can narrow that further by role or restriction, and it can never widen it beyond what Pendo itself grants.
Can I stop an agent from deleting or changing segments in Pendo (Australia)?
Yes. Restrictions in Elaichi apply per action, so you can allow reading visitors, accounts and usage from Pendo in Australia while blocking the creation, update or deletion of 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 (Australia) connection when someone leaves?
Offboarding a person in Elaichi ends their access to Pendo (Australia) at once, across every client they used. A connection they shared keeps working for everyone else on the team. If you want Pendo in Australia gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.
Does the Pendo (Australia) MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Pendo (Australia) 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 (Australia)?
Yes. Both let Claude, ChatGPT or Cursor use Pendo (Australia). 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 (Australia) call.
How is Elaichi different from Composio for Pendo (Australia)?
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 (Australia): 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 (Australia) 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.