Pendo SCIM MCP connector
The Pendo SCIM connector brings Pendo users and groups into Elaichi, so once connected, Claude, ChatGPT, Cursor, Microsoft Copilot or any MCP client can list, add, update and remove Pendo users and groups within each person's own access.
- Connects with an API key
- Free 14-day trial
- No credit card
List every Pendo user who is not in any group
Working in Pendo SCIM with Elaichi
-
List all Pendo SCIM users
-
Get single Pendo SCIM user by ID
-
List all Pendo SCIM groups
How to connect Pendo SCIM to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Pendo SCIM 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 SCIM MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
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 SCIM 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. The plugin directory lives at chatgpt.com/plugins.
Pendo SCIM 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.
Pendo SCIM MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
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 SCIM 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.
What teams do with Pendo SCIM 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 SCIM is logged.
-
IT
Onboard a new hire into Pendo
Create the Pendo user on day one and add them to the right groups from a single request, instead of clicking through the admin screen for each one.
-
People
Offboard a leaver the same day
When someone leaves, remove their Pendo user and take them out of every group they belonged to, with a record of who did it and when.
-
Security
Check who still has a Pendo seat
List every Pendo user and group, spot accounts that should have gone months ago, and clean them up before the next access review.
-
Product Operations
Keep product squads in the right groups
When teams reorganize, move people between Pendo groups so each squad sees the dashboards and guides meant for them.
-
Finance
Reconcile Pendo seats before renewal
Pull the full list of Pendo users, compare it with the headcount you are paying for, and remove the seats nobody is using.
-
Compliance
Answer an access audit in minutes
Ask which Pendo users sit in which groups and get the list back straight away, with every change already logged by name.
Try asking
- “List every Pendo user who is not in any group”
- “Create a Pendo user for Priya Shah and add her to Product”
- “Which Pendo groups does [email protected] belong to?”
What connecting Pendo SCIM gets you
6 screens from Elaichi, each doing one job for your Pendo SCIM account.
Ask Elaichi to work across your apps.
List every Pendo user who is not in any group
Create a Pendo user for Priya Shah and add her to Product
Which Pendo groups does [email protected] belong to?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask who has a Pendo seat, get answers.
Type a plain question and the Elaichi agent reads live Pendo SCIM users and groups.
Copy the endpoint
AI apps
Manage Pendo SCIM users from any MCP client.
One governed endpoint serves Claude, ChatGPT and Cursor, with no SDK and no shared API key.
Tool catalog
11 Pendo SCIM tools, no custom code needed.
Every user and group method Pendo SCIM offers is cataloged and ready to call.
Toolboxes
Each team gets its own Pendo SCIM toolbox.
IT provisions, Security reviews, People offboards, each from a toolbox scoped to their team.
Shared connections
Teammates provision Pendo users without the API key.
One person connects Pendo SCIM, shares it with teams, and nobody else sees the credential.
Audit log
Every Pendo user change is logged by name.
See when a user or group was created, changed or removed, and who did it.
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 SCIM digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch users
Pendo SCIM
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 Jake Morgan
Approve Deny -
Post the digest
Pendo SCIM
Queued
Workflows
A schedule runs the Pendo seat review itself.
Users are fetched, grouped, digested, approved by a person, then stale seats are removed in Pendo.
Pendo SCIM health
Refreshed 4 minutes ago · every 15 minutes · from the users collection
Users
1,284 ↓ 12%
Groups
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Users created
Last 14 days
By team
Share of activity
IT Admin 34%
Security 27%
People Ops 21%
Product Ops 18%
Collections and dashboards
Pendo seat counts refresh without anyone asking.
Users created over 14 days, broken down by team, computed with no model involved.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Pendo SCIM
All three can connect Pendo SCIM 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 SCIM tools | Allow or restrict single Pendo SCIM 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 SCIM 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 SCIM tools for your AI agents
11 tools are ready to call through Elaichi's MCP endpoint the moment you connect Pendo SCIM, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Pendo SCIM to Claude?
Connect Pendo SCIM in Elaichi first, which only asks for your Pendo SCIM API key, so there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in as yourself and Claude can start working with your Pendo users and groups.
Does Pendo SCIM work with ChatGPT and Cursor as well as Claude?
Yes. Once Pendo SCIM is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect Pendo SCIM once and every client you use picks it up.
What can an AI agent actually do with my Pendo SCIM data?
An agent can list every Pendo user and group, look up one person or one group, create a new Pendo user, update their details, and remove users or groups that should no longer exist. In practice that means onboarding a hire, offboarding a leaver, or answering who sits in which Pendo group, all from a plain question. Short, concrete asks such as "add Priya to the Product group" work better than long paragraphs.
Does connecting Pendo SCIM give the AI everything in my Pendo account?
No. Pendo SCIM only covers users and groups, and whatever an agent does runs inside the access of the person who signed in to Elaichi, so it cannot reach anything that person could not reach in Pendo. Elaichi can narrow that access further with roles and restrictions, and it never widens it.
Can I stop an agent from deleting or changing things in Pendo SCIM?
Yes. Restrictions in Elaichi work per action, so you can restrict deleting Pendo users or changing Pendo groups for a role or for one person while leaving listing and lookups open. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to a Pendo SCIM connection when someone leaves?
Offboarding that person in Elaichi ends their access to Pendo SCIM at once, across every client they used. A shared Pendo SCIM connection keeps working for everyone else on the team. If you want the connection gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.
Does the Pendo SCIM MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Pendo SCIM 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 SCIM?
Yes. Both let Claude, ChatGPT or Cursor use Pendo SCIM. 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 SCIM call.
How is Elaichi different from Composio for Pendo SCIM?
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 SCIM: 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 SCIM 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