# ZoomInfo SCIM MCP connector

The ZoomInfo SCIM connector lets Claude, ChatGPT, Cursor, Microsoft Copilot or the Elaichi Agent list, create, update and remove ZoomInfo users and groups, with every change running under the signed-in person's access and recorded in an audit log.

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

## Facts

| | |
| --- | --- |
| Application | ZoomInfo SCIM |
| Category | Sales Intelligence |
| AI tools | 12 |
| 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 ZoomInfo SCIM is connected

- List every ZoomInfo user who is not in any group
- Add Priya Shah to the Enterprise Sales group in ZoomInfo
- How many ZoomInfo users did we create this month?

## Connect ZoomInfo SCIM in Elaichi

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

1. Open Connections, choose Add connection, and pick ZoomInfo SCIM.
2. Optionally set Share with, then press Connect.
3. Paste a ZoomInfo SCIM API key. One person generates a token in ZoomInfo 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 ZoomInfo SCIM tools are exposed, rename them, or freeze arguments before anyone points a client at it.

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

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

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

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

## ZoomInfo 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 ZoomInfo 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 ZoomInfo 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 ZoomInfo SCIM through Elaichi

### Give a new rep a ZoomInfo seat

IT. Ask for a ZoomInfo user to be created from the name and email in the hiring note, then placed in the right group before their first call.

### Move reps between ZoomInfo groups after a reorg

Sales Operations. List who sits in each ZoomInfo group today, then move the people who changed territory without opening the admin console for each one.

### Find ZoomInfo users who are in no group

Revenue Operations. Pull every ZoomInfo user, check which ones have no group membership, and fix them so reporting lines match the sales org.

### Remove a leaver's ZoomInfo access today

Security. When someone leaves, look up their ZoomInfo user and remove it the same day, with the change logged against whoever asked for it.

### Count ZoomInfo seats before renewal

Finance. List all active ZoomInfo users and compare the total to the invoice before the contract renews, so you only pay for seats that are in use.

### Correct a ZoomInfo user's name or email

Helpdesk. When a rep changes their name or email, update the ZoomInfo user record from the ticket instead of raising it with the admin.

## Elaichi vs Zapier MCP vs Composio for ZoomInfo SCIM

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

To connect ZoomInfo SCIM to Claude, first connect it in Elaichi by pasting the API key from your ZoomInfo admin settings, with 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 ZoomInfo users and groups are available in the chat.

### Does ZoomInfo SCIM work with ChatGPT and Cursor as well as Claude?

Yes. ZoomInfo SCIM connects once in Elaichi and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. There is nothing extra to set up per client.

### What can an AI agent actually do with my ZoomInfo users and groups?

With ZoomInfo SCIM connected, an agent can list every ZoomInfo user and group, look one up, create a user or group, change a name, email or group membership, and remove a user or group. Short, concrete asks such as "add this person to the SDR group" work better than long paragraphs.

### Does connecting ZoomInfo SCIM give the AI control over every user and group?

No. Everything an agent does in ZoomInfo SCIM runs inside the access of the person who signed in, so it can only manage the ZoomInfo users and groups that person could already manage. Elaichi can narrow that further with restrictions, and it never widens it.

### Can my team share one ZoomInfo SCIM connection?

Yes. One admin connects ZoomInfo SCIM in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person behind every change to a user or group.

### Can I stop an agent from deleting or changing things in ZoomInfo SCIM?

Yes. In Elaichi you can restrict any single ZoomInfo SCIM action, such as deleting a user or deleting a group, for a role or for one person. A restricted action still shows up in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a ZoomInfo SCIM connection when someone leaves?

When someone is offboarded in Elaichi, their access to ZoomInfo SCIM through every client ends at once. A connection they shared keeps working for everyone else on the team. If you disconnect ZoomInfo SCIM in Elaichi, it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client in one step.

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

Yes. ZoomInfo 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 ZoomInfo SCIM?

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

### How is Elaichi different from Composio for ZoomInfo 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 ZoomInfo 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 12 ZoomInfo SCIM tools

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

- **List all ZoomInfo SCIM groups** (List). List groups in ZoomInfo via SCIM. Supports SCIM filter (e.g. displayName eq "Sales"), startIndex and count. Returns: id, displayName, members.
- **Get single ZoomInfo SCIM group by ID** (Get). Get a single ZoomInfo group by SCIM group id. Returns: id, displayName, members, meta. Required: id.
- **Create a ZoomInfo SCIM group** (Create). Create a group in ZoomInfo via SCIM. Required: schemas, displayName. Optional members (user ids). Returns the created group with its id.
- **Update a ZoomInfo SCIM group by ID** (Update). Replace a ZoomInfo group via SCIM (PUT): name and the full member list. Required: id, schemas, displayName.
- **ZoomInfo SCIM groups partial update** (Update). Partially update a ZoomInfo group via SCIM PATCH, e.g. add members with {"op":"add","path":"members","value":[{"value":"&lt;user id&gt;"}]} or remove with path members[value eq "&lt;user id&gt;"]. Required: group_id, schemas, Operations.
- **Delete a ZoomInfo SCIM group by ID** (Delete). Delete a ZoomInfo group via SCIM. Required: id.
- **List all ZoomInfo SCIM users** (List). List users provisioned in ZoomInfo via SCIM. Supports SCIM filter (e.g. userName eq "jane@acme.com"), startIndex and count. Returns: id, userName, name, emails, active, groups.
- **Get single ZoomInfo SCIM user by ID** (Get). Get a single ZoomInfo user by SCIM user id. Returns: id, userName, name, emails, active, groups, meta. Required: id.
- **Create a ZoomInfo SCIM user** (Create). Provision (create) a user in ZoomInfo via SCIM. Required: schemas, userName, name.givenName, name.familyName. Returns the created user with its id.
- **Update a ZoomInfo SCIM user by ID** (Update). Replace a ZoomInfo user via SCIM (PUT): send the full user; omitted attributes are cleared. Set active false to deactivate. Required: id, schemas, userName, name.
- **ZoomInfo SCIM users partial update** (Update). Partially update a ZoomInfo user via SCIM PATCH, e.g. deactivate with {"op":"replace","path":"active","value":false}. Required: user_id, schemas, Operations.
- **Delete a ZoomInfo SCIM user by ID** (Delete). Delete (deprovision) a ZoomInfo user via SCIM. Required: id.
