Unified User
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.
- Connects with an API key
- Free 14-day trial
- No credit card
List every Miro user who is not in any group
Working in Miro SCIM with Elaichi
-
List all Miro SCIM users
-
Get single Miro SCIM user by ID
-
Get single Miro SCIM group by ID
How to connect Miro SCIM to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Miro 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.
Miro 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.
Miro 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.
Miro 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.
Miro 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 Miro 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 Miro 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 Miro SCIM is logged.
-
IT
Set up a new hire in Miro
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.
-
IT
Remove a leaver from Miro the same day
Ask for the person by name, confirm the match, and delete their Miro user and group memberships in one pass.
-
People Ops
Move someone to a new team's group
When a designer switches squads, update their Miro group membership so their access follows them the same morning.
-
Security
Check who still has a Miro login
List every Miro SCIM user and compare it against the HR roster to spot accounts that should have been removed months ago.
-
Finance
Count Miro users before the renewal
Pull the full user list, break it down by group, and see how many active users you are paying for before the invoice arrives.
-
Operations
Audit Miro groups against the org chart
List all Miro groups and their members, then fix the ones that drifted after the last reorg.
Try asking
- “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”
What connecting Miro SCIM gets you
6 screens from Elaichi, each doing one job for your Miro SCIM account.
Ask Elaichi to work across your apps.
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
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask who has Miro access, in plain words.
The Elaichi Agent reads live Miro SCIM users and groups and answers from them.
Copy the endpoint
AI apps
One endpoint, every client, no shared API key.
Claude, ChatGPT and Cursor reach Miro SCIM through one governed org endpoint, no SDK.
Tool catalog
16 Miro SCIM tools, ready without code.
Users, groups, schemas and resource types, listed, created, updated and removed with no custom code.
Toolboxes
Every team gets its own Miro SCIM toolbox.
IT provisions, Security reviews, Finance counts, each from a toolbox scoped to that team.
Shared connections
Share the connection, never the API key.
One admin connects Miro SCIM and teammates work through it without seeing a credential.
Audit log
Know who removed which Miro user, and when.
Every call logs when, who, what happened, type and resource, in an append-only log.
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.
Miro SCIM digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch users
Miro 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
Miro SCIM
Queued
Workflows
A schedule starts the access review, you approve.
Miro SCIM users are fetched, grouped, drafted into a digest, approved, then posted back.
Miro 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 Admin 34%
People Ops 27%
Security 21%
Finance 18%
Collections and dashboards
Miro user counts, computed, no model involved.
Four metrics, 14 days of users created and a breakdown by team, refreshed on schedule.
For IT and engineering
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Miro SCIM tools for your AI agents
16 tools are ready to call through Elaichi's MCP endpoint the moment you connect Miro 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 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 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.
Put Miro 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