# Netskope SCIM MCP connector

The Netskope SCIM connector brings Netskope users and groups into Elaichi, so once it is connected Claude, ChatGPT, Cursor, Microsoft Copilot or the Elaichi Agent can list, create, update and remove them inside each person's own access.

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

## Facts

| | |
| --- | --- |
| Application | Netskope SCIM |
| Category | Security |
| 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 Netskope SCIM is connected

- List every Netskope group the new sales hires should join
- Which Netskope groups is Priya Shah in right now?
- Remove Dan Ortiz from the Finance group in Netskope

## Connect Netskope SCIM in Elaichi

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

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

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

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

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

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

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

### Provision a new hire on day one

IT. Create the Netskope user from the starter details and add them to the right groups before their laptop arrives.

### Pull someone out of every group fast

Security. When a contractor ends or an account looks compromised, check which Netskope groups the person is in and remove them in one pass.

### Check who is still active after offboarding

HR. Compare the list of Netskope users against the leavers list and flag anyone who should already be gone.

### Find out which groups a person belongs to

Helpdesk. When a ticket says someone cannot reach a site, look up their Netskope user and group membership without opening the admin console.

### Review group membership before an audit

Compliance. Pull every member of a sensitive Netskope group and get a plain summary of who has access and when they were added.

### Fix a name or email after a change

Identity. Update a Netskope user's details after a name change or a domain move, and confirm the record matches the directory.

## Elaichi vs Zapier MCP vs Composio for Netskope SCIM

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

Open Elaichi, choose Netskope SCIM, and paste in the API key from your Netskope tenant. 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 as the endpoint. Claude will ask you to sign in to Elaichi, and from then on Netskope SCIM is available in your chats.

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

Yes. Netskope SCIM is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, the Elaichi Agent and any other MCP client. You do not connect Netskope SCIM again for each one.

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

With Netskope SCIM connected, an agent can list your Netskope users and groups, look up one person or one group, create new users and groups, update their details and membership, replace them, and delete them. In practice that means asking which groups someone is in, provisioning a new hire, or removing a leaver from every group. Short, concrete asks such as "add Maya to the Finance group" work better than long paragraphs.

### Does connecting Netskope SCIM give the AI full admin rights?

No. Every call to Netskope SCIM runs as the person who signed in, so an agent can only see and change what that person's own Netskope SCIM key allows. Elaichi can narrow that access further with roles and restrictions, and it never widens it beyond what Netskope already permits.

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

Yes. One administrator connects Netskope SCIM with the API key and shares the connection with a team, and nobody else ever sees or handles that key. Each teammate still signs in to Elaichi as themselves, so every change to a Netskope user or group is logged under their own name.

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

Yes. Restrictions in Elaichi work per action, so you can allow looking up Netskope users and groups while restricting creating, updating, replacing or deleting them, for a role or for one person. 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 Netskope SCIM connection when someone leaves?

Offboarding the person in Elaichi ends their access to Netskope SCIM at once, across Claude, ChatGPT, Cursor, Microsoft Copilot and every other client. A shared Netskope SCIM connection keeps working for everyone else on the team. If you want it gone entirely, disconnecting Netskope SCIM once in Elaichi removes it from every client.

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

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

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

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

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

- **List all Netskope SCIM users** (List). List SCIM users in the Netskope tenant (GET /api/v2/scim/Users). Paginated with startIndex/count (SCIM ListResponse; results in Resources). Supports a SCIM filter, e.g. userName eq "jane@acme.com". Returns id, userName, name, emails, active, externalId.
- **Get single Netskope SCIM user by ID** (Get). Get one SCIM user by id (GET /api/v2/scim/Users/{id}). The id is the Netskope SCIM user id (UUID) returned by list or create. Returns id, userName, name, emails, active, externalId.
- **Create a Netskope SCIM user** (Create). Create a SCIM user in Netskope (POST /api/v2/scim/Users). The user becomes a SCIM user that can be added to groups; enrollment is by email invite. Required: schemas (["urn:ietf:params:scim:schemas:core:2.0:User"]), userName. Returns the created user with its id (201).
- **Update a Netskope SCIM user by ID** (Update). Update a SCIM user with SCIM PATCH operations (PATCH /api/v2/scim/Users/{id}), e.g. deactivate with {"op":"replace","path":"active","value":false} or change name.givenName. Users created via REST API v2 must be changed via REST API v2. The id is the SCIM user id. Required: id, schemas, Operations.
- **Delete a Netskope SCIM user by ID** (Delete). Delete a SCIM user (DELETE /api/v2/scim/Users/{id}). The id is the SCIM user id. Required: id. Returns 204 with an empty body.
- **Netskope SCIM users replace** (Action). Replace a SCIM user (PUT /api/v2/scim/Users/{id}, SCIM 2.0 full replace): send the complete user; attributes left out are cleared. Prefer update (PATCH) for partial changes. user_id is the SCIM user id. Required: user_id, schemas, userName. Returns the updated user.
- **List all Netskope SCIM groups** (List). List SCIM groups in the Netskope tenant (GET /api/v2/scim/Groups). Paginated with startIndex/count (SCIM ListResponse; results in Resources). Supports a SCIM filter, e.g. displayName eq "Engineering". Returns id, displayName, externalId.
- **Get single Netskope SCIM group by ID** (Get). Get one SCIM group by id (GET /api/v2/scim/Groups/{id}). Pass attributes=members to include members (needs the tenant flag "SCIM Query Attributes Support for Group Membership"). The id is the SCIM group id. Returns id, displayName, externalId and optionally members.
- **Create a Netskope SCIM group** (Create). Create a SCIM group (POST /api/v2/scim/Groups), optionally with initial members [{"value": "&lt;user id&gt;"}]. Required: schemas (["urn:ietf:params:scim:schemas:core:2.0:Group"]), displayName. Returns the created group with its id (201).
- **Update a Netskope SCIM group by ID** (Update). Change a SCIM group with SCIM PATCH operations (PATCH /api/v2/scim/Groups/{id}): add members ({"op":"add","path":"members","value":[{"value":"&lt;user id&gt;"}]}), remove members (path members[value eq "&lt;user id&gt;"]) or replace displayName. The id is the SCIM group id. Required: id, schemas, Operations. Returns 204 with an empty body.
- **Delete a Netskope SCIM group by ID** (Delete). Delete a SCIM group (DELETE /api/v2/scim/Groups/{id}). The id is the SCIM group id. Required: id. Returns 204 with an empty body.
- **Netskope SCIM groups replace** (Action). Replace a SCIM group (PUT /api/v2/scim/Groups/{id}, SCIM 2.0 full replace): send displayName and the complete members list; members left out are removed. Prefer update (PATCH) to add or remove single members. group_id is the SCIM group id. Required: group_id, schemas, displayName. Returns the updated group.
