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

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

## Facts

| | |
| --- | --- |
| Application | Docker Hub SCIM |
| Category | Application Development |
| AI tools | 9 |
| 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 Docker Hub SCIM is connected

- List every Docker Hub user and flag any without a last name
- Create a Docker Hub user for Priya Nair, priya@acme.com
- Update Sam Ortiz's Docker Hub email to sam.ortiz@acme.com

## Connect Docker Hub SCIM in Elaichi

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

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

## Docker Hub 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.

## Docker Hub 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`.

## Docker Hub 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.

## Docker Hub 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.

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

### Provision a Docker Hub seat on day one

IT. Create the new engineer's Docker Hub user from a name and email before their first standup, without opening the admin console.

### Fix a user's name or email

IT. Update a Docker Hub user when someone changes their name or moves to a new email address, in one ask.

### Review who holds a Docker Hub seat

Security. List every Docker Hub user, check each one against the directory, and flag accounts that no longer belong to anyone on staff.

### Look up one teammate's Docker Hub account

Engineering. Pull a single Docker Hub user by ID to confirm their status before adding them to a repository or team.

### Pull the user list for an access audit

Compliance. Gather the full Docker Hub user roster with status for a quarterly review, straight from the source rather than a stale spreadsheet.

### Check what Docker Hub SCIM supports

Platform. Read the Docker Hub SCIM service provider config, resource types and schemas before changing how your identity provider syncs users.

## 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. Endpoint: 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](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 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 my team share one Docker Hub SCIM connection?

Yes. One admin connects Docker Hub SCIM and shares it with a team in Elaichi, and nobody else ever handles the API key. Each person still signs in to Elaichi as themselves, so the audit log names who created or updated each Docker Hub user.

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

## All 9 Docker Hub SCIM tools

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

- **List all Docker Hub SCIM users** (List). List users. Returns paginated users for an organization. Use `startIndex` and `count` query parameters to receive paginated results. **Sorting:** Sorting allows you to specify the order in which resources are returned by specifyi…
- **Get single Docker Hub SCIM user by ID** (Get). Get a user. Returns a user by ID. Required: id.
- **Create a Docker Hub SCIM user** (Create). Create user. Creates a user. If the user already exists by email, they are assigned to the organization on the "company" team. Required: schemas, userName.
- **Update a Docker Hub SCIM user by ID** (Update). Update a user. Updates a user. This route is used to change the user's name, activate, and deactivate the user. Required: schemas, userName.
- **Docker Hub SCIM service provider config get current** (Get). Get service provider config. Returns a service provider config for Docker's configuration.
- **List all Docker Hub SCIM resource types** (List). List resource types. Returns all resource types supported for the SCIM configuration.
- **Get single Docker Hub SCIM resource type by ID** (Get). Get a resource type. Returns a resource type by name. Required: id.
- **List all Docker Hub SCIM schemas** (List). List schemas. Returns all schemas supported for the SCIM configuration.
- **Get single Docker Hub SCIM schema by ID** (Get). Get a schema. Returns a schema by ID. Required: id.
