# PingOne MCP connector

Connect PingOne to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent can look up, create and update PingOne users, licenses, roles and organizations, with every action running inside your access and logged.

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

## Facts

| | |
| --- | --- |
| Application | PingOne |
| Category | SSO |
| AI tools | 581 |
| Authentication | App credentials |
| 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 PingOne is connected

- Find the PingOne user for Priya Shah and her identity provider
- Resend the verification code to the new starter in Finance
- How many active identities did we use against each license last month

## Connect PingOne in Elaichi

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

1. Open Connections, choose Add connection, and pick PingOne.
2. Optionally set Share with, then press Connect.
3. Paste your PingOne app credentials. PingOne authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.

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

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

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

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

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

## PingOne 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 PingOne 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 PingOne 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 PingOne through Elaichi

### Find the user before the call ends

Help desk. Pull up a PingOne user by name or ID while the caller is still on the line, and see which identity provider they sign in through before guessing at the problem.

### Resend a verification code in seconds

Help desk. When a new starter never got their verification email, ask for it to be resent from PingOne without opening the admin console.

### Create accounts for Monday's joiners

HR. Hand over the list of new hires and have their PingOne users created or imported in one go, ready before their first morning.

### Check who signs in through which provider

Security. List the identity provider attached to each PingOne user and move anyone still on the wrong provider over to the right one.

### Match active identity counts to the bill

Finance. Ask for active identity counts by license and by date range in PingOne, then compare them to what the invoice says you are paying for.

### Pull roles and organizations for the audit

Compliance. Get a current list of PingOne roles, organizations and licenses when the auditor asks, without a ticket to IT and a week of waiting.

## Elaichi vs Zapier MCP vs Composio for PingOne

All three can connect PingOne 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 PingOne tools | Allow or restrict single PingOne 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 PingOne 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 PingOne to Claude?

Connect PingOne in Elaichi first, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. PingOne's sign-in step is a short form in Elaichi where you enter the app credentials from your PingOne environment. There is no OAuth application to register and no client ID or secret to generate. Once saved, Claude can work with your PingOne users, licenses, roles and organizations.

### Does PingOne work with ChatGPT and Cursor as well as Claude?

Yes. The same PingOne connection in Elaichi works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect PingOne once, and every client uses the same endpoint, https://api.elaichi.ai/mcp.

### What can an AI agent actually do with my PingOne data?

An agent can look up a PingOne user, check which identity provider they sign in through, create or update accounts, resend a verification code, and remove an account when someone leaves. It can also list your PingOne licenses, roles and organizations, and report active identity counts for a date range or a license. Short, concrete asks work better than long sentences, so 'find the PingOne user for Priya Shah' gets a cleaner answer than a paragraph.

### Does connecting PingOne give the AI access to every user and environment?

No. An agent only sees what the person who connected PingOne can already see, so PingOne's own roles and environment permissions still apply. Elaichi can narrow that further by restricting specific actions, but it can never widen access beyond what PingOne has already granted that person.

### Can my team share one PingOne connection?

Yes. One admin connects PingOne in Elaichi and shares the connection with a team, and nobody else ever handles the app credentials. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who looked up or changed a PingOne user, not a shared account.

### Can I stop an agent from deleting or changing users in PingOne?

Yes. In Elaichi, restrictions are set per action, on a role or on one person, so the help desk can resend verification codes while deleting a PingOne user is restricted for everyone except your identity admins. 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 PingOne connection when someone leaves?

Offboarding someone in Elaichi ends their access to the PingOne connection at once, across every client. A shared PingOne connection keeps working for everyone else on the team. If you disconnect PingOne once in Elaichi, it is removed from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.

### Does the PingOne MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. PingOne 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 PingOne?

Yes. Both let Claude, ChatGPT or Cursor use PingOne. 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 PingOne call.

### How is Elaichi different from Composio for PingOne?

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 PingOne: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 581 PingOne tools

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

- **List all PingOne users** (List). List users in the connected PingOne environment. Filter with a SCIM filter on attributes such as username, email, population.id or lifecycle.status, for example username eq "jdoe".
- **Get single PingOne user by ID** (Get). Get a user in the connected PingOne environment by user ID. Required: id.
- **PingOne users verify** (Verify). Verify user. Verify a PingOne user account using the verification code sent to the user's email address Required: user_id.
- **PingOne users send resend verification code** (Send). Send/resend user verification code. Resend a verification code to a PingOne user who lost or did not receive the original code Required: user_id.
- **Create a PingOne user** (Create). Create user. Add a new PingOne user resource to a specified environment
- **PingOne users create import** (Create). Create user (import). Import a new PingOne user and set the user's password as part of the create operation
- **PingOne users create import external password** (Create). Create user import external password. Import a PingOne user whose password remains managed by an external directory through a gateway configuration
- **Delete a PingOne user by ID** (Delete). Delete user. Delete a PingOne user resource from the directory
- **PingOne users list identity provider** (List). Read user identity provider. Retrieve the authoritative identity provider associated with a single PingOne user resource Required: user_id.
- **PingOne users update identity provider** (Update). Update user identity provider. Update the identity provider associated with a specified PingOne user Required: user_id.
- **PingOne users partial update** (Update). Update user. Update a PingOne user's attribute properties with PATCH, modifying only the values specified in the request body Required: user_id.
- **PingOne users update using JSON array** (Update). Update user using JSON array. Update a PingOne user's attribute properties using a JSON array of SCIM PATCH operations Required: user_id.
- **Update a PingOne user by ID** (Update). Update user. Replace a PingOne user's attribute properties with PUT, removing any existing values omitted from the request body
- **List all PingOne licenses** (List). List the licenses of a PingOne organization, including package, status, user and environment limits. Required: org_id (from organizations.list).
- **Get single PingOne license by ID** (Get). Get a PingOne license by ID. Required: id and org_id.
- **PingOne licenses list license name** (List). Read one license name. Retrieve the name property value for a specified license in a PingOne organization Required: org_id, license_id.
- **PingOne licenses update license name** (Update). Update one license name. Update the custom name property value for a specified license in a PingOne organization Required: org_id, license_id.
- **List all PingOne organizations** (List). List the PingOne organizations the client application can access. Use the organization ID with licenses.list.
- **Get single PingOne organization by ID** (Get). Get a PingOne organization by ID, including its type and billing connections. Required: id.
- **List all PingOne roles** (List). List the built-in PingOne administrator roles with their permissions and the scopes they apply to.
- **Get single PingOne role by ID** (Get). Get a PingOne administrator role by ID, including its permissions. Required: id.
- **PingOne active identity counts list date range** (List). Read active identity counts by date range. Retrieve active identity counts in a PingOne environment starting from a specified date through the current date
- **PingOne active identity counts list license** (List). Read active identity counts by license. Retrieve active identity counts per PingOne license, aggregated by calendar month or license year Required: org_id, license_id.
- **List all PingOne active identity counts** (List). Read active identity counts (Deprecated). Retrieve active identity counts in a PingOne environment over a date range, sampled by day or month
- **List all PingOne administrator security** (List). Read administrator security. Retrieve the administrator sign-on security configuration, including MFA enforcement and authentication method, for a PingOne environment
- **Update a PingOne administrator security by ID** (Update). Update administrator security (enhanced). Update a PingOne environment's administrator sign-on configuration to require PingOne MFA for all administrator sign-ons
- **PingOne administrator security update external idp** (Update). Update administrator security (external IdP). Update a PingOne environment's administrator sign-on configuration to use an external identity provider for administrator authentication
- **PingOne administrator security update populations hybrid** (Update). Update administrator security populations (hybrid). Update the populations requiring MFA for administrator sign-on in a PingOne environment configured for hybrid authentication
- **Create a PingOne agreement languages resource** (Create). Create language. Required permission: Required: agreement_id.
- **Delete a PingOne agreement languages resource by ID** (Delete). Delete language. Required permission: Required: agreement_id.
- **List all PingOne agreement languages resources** (List). Read all languages. Required permission: Required: agreement_id.
- **Get single PingOne agreement languages resource by ID** (Get). Read one language. Required permission: Required: agreement_id.
- **Update a PingOne agreement languages resource by ID** (Update). Update language. Required permission: Required: agreement_id.
- **Create a PingOne agreement revisions resource** (Create). Create revision. Required permission: Required: agreement_id, language_id.
- **Delete a PingOne agreement revisions resource by ID** (Delete). Delete revision. Required permission: Required: agreement_id, language_id.
- **List all PingOne agreement revisions resources** (List). Read all revisions. Required permission: Required: agreement_id, language_id.
- **Get single PingOne agreement revisions resource by ID** (Get). Read one revision. Required permission: Required: agreement_id, language_id.
- **Create a PingOne agreements resource** (Create). Create agreement. Required permission:
- **Delete a PingOne agreements resource by ID** (Delete). Delete agreement. Required permission:
- **List all PingOne agreements resources** (List). Read all agreements. Required permission:
- **Get single PingOne agreements resource by ID** (Get). Read one agreement. Required permission:
- **Update a PingOne agreements resource by ID** (Update). Update agreement. Required permission:
- **Create a PingOne alerting** (Create). Create alert channel (email). Create an email alert channel for a PingOne environment to notify administrators about resource-state changes
- **Delete a PingOne alerting by ID** (Delete). Delete alert channel. Delete an alert channel from a PingOne environment
- **List all PingOne alerting** (List). Read all alert channels per environment. Retrieve all alert channels configured for a PingOne environment
- **Update a PingOne alerting by ID** (Update). Update alert channel. Update an alert channel's addresses, name, or included and excluded alert types for a PingOne environment
- **Create a PingOne application attribute mapping** (Create). Create application attribute mapping. Add a custom attribute mapping to a PingOne application for use in ID tokens or SAML assertions Required: app_id.
- **Delete a PingOne application attribute mapping by ID** (Delete). Delete application attribute mapping. Delete an attribute mapping from a PingOne application by application ID and attribute ID Required: app_id.
- **List all PingOne application attribute mapping** (List). Read all application attribute mappings. List all attribute mappings configured for a PingOne application Required: app_id.
- **Get single PingOne application attribute mapping by ID** (Get). Read one application attribute mapping. Retrieve a single attribute mapping for a PingOne application by attribute ID Required: app_id.
- ...and 531 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
