# Miro SCIM MCP connector

Connect Miro SCIM to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot or any MCP client can list, create, update and remove Miro users and groups, each change made as the signed-in person and logged.

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

## Facts

| | |
| --- | --- |
| Application | Miro SCIM |
| Category | Unified User |
| AI tools | 16 |
| 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 Miro SCIM is connected

- List every Miro user who is not in any group
- Add Priya Shah to the Design group in Miro
- Show me all Miro groups and how many members each has

## Connect Miro SCIM in Elaichi

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

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

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

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

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

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

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

### Set up a new hire in Miro

IT. Create the Miro user from the details in the welcome email and place them in the right group before their first standup. No ticket queue, no waiting on an admin.

### Remove a leaver from Miro the same day

IT. Ask for the person by name, confirm the match, and delete their Miro user and group memberships in one pass.

### Move someone to a new team's group

People Ops. When a designer switches squads, update their Miro group membership so their access follows them the same morning.

### Check who still has a Miro login

Security. List every Miro SCIM user and compare it against the HR roster to spot accounts that should have been removed months ago.

### Count Miro users before the renewal

Finance. Pull the full user list, break it down by group, and see how many active users you are paying for before the invoice arrives.

### Audit Miro groups against the org chart

Operations. List all Miro groups and their members, then fix the ones that drifted after the last reorg.

## Elaichi vs Zapier MCP vs Composio for Miro SCIM

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

Connect Miro SCIM in Elaichi by pasting the SCIM API key from your Miro admin settings, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. There is no OAuth application to register in Miro and no client ID or secret to generate. From then on you sign in to Elaichi as yourself and Claude can work with your Miro users and groups.

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

Yes. Once Miro SCIM is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Miro SCIM once and every client picks it up.

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

With Miro SCIM connected, an agent can list the people and groups in your Miro organization, look up one user or group, create new users and groups, update names, emails or memberships, and remove users or groups that should not be there. It can also read the Miro SCIM setup details, such as which fields Miro accepts and what the provisioning service supports. Short, concrete asks work best, such as add Priya to the Design group.

### Does connecting Miro SCIM give the AI control over my whole Miro organization?

A Miro SCIM connection carries the access of the API key it was made with, and in Elaichi each person signs in as themselves, so every call is tied to a named person and runs inside the access their organization gave them. Elaichi can narrow what any role or person can do with Miro SCIM, for example reads only, and it never widens access beyond what Miro itself allows.

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

Yes. One admin connects Miro SCIM in Elaichi and shares the connection with the IT or People team, and nobody else ever sees or handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log names who created, updated or removed each Miro user.

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

Yes. In Elaichi, restrictions are set per action on a role or on one person, so you can let the help desk create Miro users while keeping deleting users and groups to a couple of admins. 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 Miro SCIM connection when someone leaves?

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

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

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

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

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

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

- **List all Miro SCIM users** (List). List the users in your Miro organization. Returns user records including id, userName, displayName, name, userType, active, emails, photos, groups, and roles. Max 1000 per page; supports SCIM filter expressions via filter.
- **Get single Miro SCIM user by ID** (Get). Get a single Miro user by id. Returns: schemas, id, meta, userName, name, displayName, userType, active, emails, photos, groups, roles, preferredLanguage, urn:ietf:params:scim:schemas:extension:enterprise:2.0:User. Required: id. Only members of the organization can be fetched; guest users cannot.
- **Update a Miro SCIM user by ID** (Update). Update an existing Miro user by id with a SCIM PatchOp. Returns the updated user record including id, userName, displayName, active, and roles. Required: id, schemas, Operations. The userType license cannot be downgraded.
- **Create a Miro SCIM user** (Create). Create a user in the Miro organization via SCIM. Returns the created user including id, userName, name, emails, active, and meta. Required: userName. All newly provisioned users are added to the default team.
- **Delete a Miro SCIM user by ID** (Delete). Delete a Miro SCIM user by id. Returns an empty 204 response on success. Required: id. The last admin of a team or organization and guest-role users cannot be deleted; deleted users' boards transfer to the oldest admin team member.
- **Create a Miro SCIM group** (Create). Create a new Miro user group in the organization. Returns: schemas, id, meta, displayName, members. Optionally accepts an initial members list. Required: displayName.
- **Delete a Miro SCIM group by ID** (Delete). Delete a Miro user group from the organization by id. Only the group and its memberships are removed — member users are kept. Returns an empty 204 response on success. Required: id.
- **Get single Miro SCIM group by ID** (Get). Get a single Miro user group by id. Returns: schemas, id, meta, displayName, members. Required: id.
- **List all Miro SCIM groups** (List). List Miro user groups in the organization along with their members. Returns: schemas, id, displayName, members, meta. Supports SCIM filter expressions (e.g. displayName eq "Product Team"); max 1000 results per page.
- **Update a Miro SCIM group by ID** (Update). Patch a Miro user group by id to add, remove, or replace members or update its displayName via SCIM operations. Returns the updated group: id, displayName, members, meta. displayName is capped at 60 characters. Required: id.
- **List all Miro SCIM resource types** (List). List the SCIM resource types supported by Miro. Returns: schemas, id, name, description, endpoint, schema, schemaExtensions. Currently only Users and Groups are supported.
- **List all Miro SCIM resource types resourcetypes** (List). Get a single SCIM resource type in Miro by its resource name (e.g. User or Group). Returns: schemas, id, name, description, endpoint, schema, schemaExtensions. Required: resource.
- **List all Miro SCIM schemas** (List). List SCIM schemas in Miro, retrieving metadata about Users, Groups, and supported extension attributes. Returns: schemas, id, name, description, attributes, meta.
- **List all Miro SCIM schemas SCIM** (List). Get a SCIM schema definition from Miro by its uri. Returns: id, name, description, attributes, meta. Required: uri.
- **List all Miro SCIM service provider configs** (List). Get the Miro SCIM Service Provider Config, describing the supported operations and basic SCIM API configuration. Returns: schemas, documentationUri, patch, bulk, filter, changePassword, sort, etag, authenticationSchemes.
- **Update a Miro SCIM users SCIM by ID** (Update). Replace an existing SCIM user in Miro, overwriting the resource with the supplied user attributes. Returns: schemas, id, meta, userName, name, displayName, userType, active, emails, photos, groups, roles, preferredLanguage, urn:ietf:params:scim:schemas:extension:enterprise:2.0:User. Required: id.
