# 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.

Source: https://elaichi.ai/connectors/pendoscim/

## Facts

| | |
| --- | --- |
| Application | Pendo SCIM |
| Category | Analytics |
| AI tools | 11 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Pendo SCIM is connected

- 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 dana@acme.com belong to?

## Connect Pendo SCIM in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Pendo SCIM.
2. Optionally set Share with, then press Connect.
3. Paste a Pendo SCIM API key. One person generates a token in Pendo SCIM and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Pendo SCIM tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Pendo SCIM MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Pendo SCIM MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

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.
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.

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

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Pendo SCIM tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Pendo SCIM through Elaichi

### Onboard a new hire into Pendo

IT. 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.

### Offboard a leaver the same day

People. 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.

### Check who still has a Pendo seat

Security. List every Pendo user and group, spot accounts that should have gone months ago, and clean them up before the next access review.

### Keep product squads in the right groups

Product Operations. When teams reorganize, move people between Pendo groups so each squad sees the dashboards and guides meant for them.

### Reconcile Pendo seats before renewal

Finance. Pull the full list of Pendo users, compare it with the headcount you are paying for, and remove the seats nobody is using.

### Answer an access audit in minutes

Compliance. Ask which Pendo users sit in which groups and get the list back straight away, with every change already logged by name.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### 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 my team share one Pendo SCIM connection?

Yes. One admin connects Pendo SCIM with the API key and shares the connection with a team in Elaichi, and nobody else on that team ever handles the key. Each person still signs in to Elaichi as themselves, so the audit log names the actual person who created or removed a Pendo user.

### 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.

## All 11 Pendo SCIM tools

Every tool below is callable through https://api.elaichi.ai/mcp once Pendo SCIM is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Pendo SCIM users** (List). List users provisioned in Pendo through SCIM. Supports SCIM filter (e.g. userName eq "jane@acme.com"). Returns users with id, userName, name, emails, active and groups.
- **Get single Pendo SCIM user by ID** (Get). Get a single Pendo SCIM user by id. Returns id, userName, name, emails, active, groups and meta. Required: id.
- **Delete a Pendo SCIM user by ID** (Delete). Delete a user from Pendo via SCIM, removing their access to the subscription. Irreversible. Required: id. Returns an empty response on success.
- **Create a Pendo SCIM user** (Create). Provision a new user in Pendo via SCIM. Required: userName, name.givenName, name.familyName, active. Returns the created user with its id.
- **Update a Pendo SCIM user by ID** (Update). Replace a Pendo SCIM user's attributes (full PUT; omitted attributes are cleared). Required: id, userName, name.givenName, name.familyName, active. Returns the updated user.
- **Pendo SCIM users partial update** (Update). Partially update a Pendo SCIM user with SCIM PatchOp operations, e.g. deactivate with op replace, path active, value false. Required: user_id, Operations. Returns the updated user.
- **List all Pendo SCIM groups** (List). List groups provisioned in Pendo through SCIM; IdP groups appear as teams in Pendo. Supports SCIM filter (e.g. displayName eq "Engineering"). Returns id, displayName and members.
- **Get single Pendo SCIM group by ID** (Get). Get a single Pendo SCIM group by id. Returns id, displayName, members and meta. Required: id.
- **Create a Pendo SCIM group** (Create). Push a new group to Pendo via SCIM; it appears as a team in Pendo. Required: displayName. Returns the created group with its id.
- **Update a Pendo SCIM group by ID** (Update). Update a Pendo SCIM group with SCIM PatchOp operations, e.g. add or remove members or rename it. Required: id, Operations. Returns the updated group or an empty response.
- **Delete a Pendo SCIM group by ID** (Delete). Delete a SCIM-pushed group (team) from Pendo. Irreversible. Required: id. Returns an empty response on success.
