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.
- Connects with an API key
- Free 14-day trial
- No credit card
List every Netskope group the new sales hires should join
Working in Netskope SCIM with Elaichi
-
List all Netskope SCIM users
-
Get single Netskope SCIM user by ID
-
List all Netskope SCIM groups
How to connect Netskope SCIM to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Netskope 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.
Netskope 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.
Netskope 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.
Netskope 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.
Netskope 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 Netskope 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 Netskope 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 Netskope SCIM is logged.
-
IT
Provision a new hire on day one
Create the Netskope user from the starter details and add them to the right groups before their laptop arrives.
-
Security
Pull someone out of every group fast
When a contractor ends or an account looks compromised, check which Netskope groups the person is in and remove them in one pass.
-
HR
Check who is still active after offboarding
Compare the list of Netskope users against the leavers list and flag anyone who should already be gone.
-
Helpdesk
Find out which groups a person belongs to
When a ticket says someone cannot reach a site, look up their Netskope user and group membership without opening the admin console.
-
Compliance
Review group membership before an audit
Pull every member of a sensitive Netskope group and get a plain summary of who has access and when they were added.
-
Identity
Fix a name or email after a change
Update a Netskope user's details after a name change or a domain move, and confirm the record matches the directory.
Try asking
- “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”
What connecting Netskope SCIM gets you
6 screens from Elaichi, each doing one job for your Netskope SCIM account.
Ask Elaichi to work across your apps.
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
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Netskope SCIM users in plain language.
Three starter prompts, answers pulled from live Netskope SCIM users and groups.
Copy the endpoint
AI apps
One endpoint for Claude, ChatGPT and Cursor.
Every MCP client reaches Netskope SCIM through one org endpoint, no SDK, no shared API key.
Tool catalog
12 Netskope SCIM tools, no code needed.
Users and groups covered end to end, listed, created, updated, replaced and deleted.
Toolboxes
Every team gets its own Netskope SCIM toolbox.
Helpdesk sees lookups, Security sees group changes, each scoped to the team that needs it.
Shared connections
Share one Netskope SCIM connection, keep the key.
Teammates manage users and groups through a connection without ever seeing the API key.
Audit log
Know who changed every user and group.
Each Netskope SCIM call is logged with who, when, what happened and which resource.
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.
Netskope SCIM digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch users
Netskope 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
Netskope SCIM
Queued
Workflows
A schedule starts the work, a person approves.
New Netskope SCIM users are fetched, grouped, drafted into a digest, approved and posted back.
Netskope 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 Operations 34%
Security 27%
Helpdesk 21%
HR 18%
Collections and dashboards
Netskope SCIM health, computed without a model.
Four metrics, fourteen days of users created, and a breakdown by team, refreshed on schedule.
For IT and engineering
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Netskope SCIM tools for your AI agents
12 tools are ready to call through Elaichi's MCP endpoint the moment you connect Netskope 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 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 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.
Put Netskope 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