Docker Hub SCIM MCP connector
Connect Docker Hub SCIM to Elaichi and Claude, ChatGPT, Cursor and Microsoft Copilot can list, create and update Docker Hub users within the access of the person asking, with every change recorded in an audit log.
- Connects with an API key
- Free 14-day trial
- No credit card
List every Docker Hub user and flag any without a last name
Working in Docker Hub SCIM with Elaichi
-
List all Docker Hub SCIM users
-
Get single Docker Hub SCIM user by ID
-
Docker Hub SCIM service provider config get current
How to connect Docker Hub SCIM to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Docker Hub 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.
Docker Hub 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.
Docker Hub 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.
Docker Hub 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.
Docker Hub 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 Docker Hub 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 Docker Hub 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 Docker Hub SCIM is logged.
-
IT
Provision a Docker Hub seat on day one
Create the new engineer's Docker Hub user from a name and email before their first standup, without opening the admin console.
-
IT
Fix a user's name or email
Update a Docker Hub user when someone changes their name or moves to a new email address, in one ask.
-
Security
Review who holds a Docker Hub seat
List every Docker Hub user, check each one against the directory, and flag accounts that no longer belong to anyone on staff.
-
Engineering
Look up one teammate's Docker Hub account
Pull a single Docker Hub user by ID to confirm their status before adding them to a repository or team.
-
Compliance
Pull the user list for an access audit
Gather the full Docker Hub user roster with status for a quarterly review, straight from the source rather than a stale spreadsheet.
-
Platform
Check what Docker Hub SCIM supports
Read the Docker Hub SCIM service provider config, resource types and schemas before changing how your identity provider syncs users.
Try asking
- “List every Docker Hub user and flag any without a last name”
- “Create a Docker Hub user for Priya Nair, [email protected]”
- “Update Sam Ortiz's Docker Hub email to [email protected]”
What connecting Docker Hub SCIM gets you
6 screens from Elaichi, each doing one job for your Docker Hub SCIM account.
Ask Elaichi to work across your apps.
List every Docker Hub user and flag any without a last name
Create a Docker Hub user for Priya Nair, [email protected]
Update Sam Ortiz's Docker Hub email to [email protected]
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Docker Hub users in plain language.
Starter prompts pull live Docker Hub SCIM users, schemas and config into one answer.
Copy the endpoint
AI apps
One endpoint, every client, no shared API key.
Claude, ChatGPT and Cursor reach Docker Hub SCIM through one governed org endpoint, no SDK.
Tool catalog
9 Docker Hub SCIM tools, no code needed.
Users, schemas, resource types and service provider config, listed with resources and methods.
Toolboxes
Each team gets its own toolbox.
Scope Docker Hub SCIM toolboxes to IT, Security, Platform or Compliance, each team seeing its own.
Shared connections
Teammates work through it, never see the key.
The connections table shows who connected Docker Hub SCIM and which teams and members share it.
Audit log
Know who changed which Docker Hub user.
Every Docker Hub SCIM call lands in the log with when, who, action, type and 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.
Docker Hub SCIM digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch users
Docker Hub 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
Docker Hub SCIM
Queued
Workflows
Schedules run the Docker Hub user review.
Users fetched, grouped, drafted into a digest, approved by a person, then posted back.
Docker Hub SCIM health
Refreshed 4 minutes ago · every 15 minutes · from the users collection
Users
1,284 ↓ 12%
Schemas
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Users created
Last 14 days
By team
Share of activity
IT Admin 34%
Security 27%
Platform 21%
Engineering EMEA 18%
Collections and dashboards
Docker Hub user numbers, computed, never asked for.
Four metrics, 14 days of users created, a team breakdown, refreshed on schedule, no model.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Docker Hub SCIM
All three can connect Docker Hub 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 Docker Hub SCIM tools | Allow or restrict single Docker Hub 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 Docker Hub 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.
Docker Hub SCIM tools for your AI agents
9 tools are ready to call through Elaichi's MCP endpoint the moment you connect Docker Hub 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 Docker Hub SCIM to Claude?
Connect Docker Hub SCIM in Elaichi by pasting the SCIM API key from your Docker Hub organization settings; there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Docker Hub SCIM is ready to use in the chat.
Does Docker Hub SCIM work with ChatGPT and Cursor as well as Claude?
Yes. Docker Hub SCIM is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. There is nothing separate to set up for each client.
What can an AI agent actually do with my Docker Hub SCIM users?
An agent connected to Docker Hub SCIM can list your Docker Hub users, look up one by ID, create a new user and update an existing one, for example changing a name or an email address. It can also read the service provider config, resource types and schemas, so it knows which fields Docker Hub accepts. Short, concrete asks work best, such as create a Docker Hub user for Priya Nair.
Does connecting Docker Hub SCIM give the AI full control of my Docker Hub organization?
No. A Docker Hub SCIM connection can only do what its API key allows, and every person uses it signed in to Elaichi as themselves, so what an agent can do follows that person's role in Elaichi. Elaichi can narrow that access with restrictions, and it never widens it beyond what the Docker Hub SCIM key already permits.
Can I stop an agent from creating or changing users in Docker Hub SCIM?
Yes. Restrictions in Elaichi work per action, so you can allow listing and looking up Docker Hub users while restricting creating or updating them, set on a role or on 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 Docker Hub SCIM connection when someone leaves?
Offboarding a person in Elaichi ends their access to Docker Hub SCIM at once. A shared Docker Hub SCIM connection keeps working for everyone else on the team. Disconnecting Docker Hub SCIM once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.
Does the Docker Hub SCIM MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Docker Hub 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 Docker Hub SCIM?
Yes. Both let Claude, ChatGPT or Cursor use Docker Hub 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 Docker Hub SCIM call.
How is Elaichi different from Composio for Docker Hub 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 Docker Hub 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 Docker Hub 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