Miro MCP connector
Connect Miro to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot or any MCP client can search boards, read and reply to comments, update canvases and pull table rows as the person who signed in.
- Connects over OAuth
- Free 14-day trial
- No credit card
Find the boards from last week's product kickoff
Working in Miro with Elaichi
-
Image get data
-
Image get upload URL
-
Image get URL
How to connect Miro to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Miro 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 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 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 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 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 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 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 is logged.
-
Design
Turn a review into resolved comments
After a design review, ask for every open comment on the board, draft replies, and resolve the ones that are done. The thread history stays in Miro where the team expects it.
-
Product
Find the board from last quarter's kickoff
Search across boards by name or topic instead of scrolling through the dashboard. Pull up the roadmap board, read what is on the canvas, and summarize it for someone who missed the session.
-
Marketing
Spin up a campaign planning board
Create a fresh board for the next launch, add images from the brief, and lay out the first draft of the canvas so the team starts from something rather than a blank space.
-
Research
Keep a findings table in step
Create a table on the research board and sync its rows from interview notes, so the synthesis wall reflects what was actually heard without someone retyping it.
-
Engineering
Read a prototype before the standup
Ask what a prototype on the board contains and how its screens connect, then create a new prototype from the agreed flow so the handoff is on the canvas, not in a chat.
-
Operations
Close out a workshop board
After a workshop, list the comments left by participants, reply to the ones that need an answer, and resolve the rest so the board is clean for the follow-up.
Try asking
- “Find the boards from last week's product kickoff”
- “Summarize the open comments on the onboarding flow board”
- “Create a retro board for the design team”
What connecting Miro gets you
6 screens from Elaichi, each doing one job for your Miro account.
Ask Elaichi to work across your apps.
Find the boards from last week's product kickoff
Summarize the open comments on the onboarding flow board
Create a retro board for the design team
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Miro boards in plain language.
Search boards, read comments and pull table rows by asking the Elaichi agent.
Copy the endpoint
AI apps
Use Miro from Claude, ChatGPT, Cursor or Microsoft Copilot.
One governed endpoint, connected once over OAuth, with no SDK and no shared API key.
Tool catalog
20 Miro tools, ready without writing code.
Boards, canvases, comments, tables, images and prototypes, covered with no custom code.
Toolboxes
Every team gets its own Miro toolbox.
Design, product and marketing each see the Miro tools their work needs.
Shared connections
Share one Miro connection without sharing credentials.
Teammates work through the Miro account one person connected, never seeing a credential.
Audit log
Every Miro action is logged with a name.
See who created a board, replied to a comment or changed a canvas, and when.
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 digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch boards
Miro
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
Queued
Workflows
A schedule starts Miro work and finishes it.
New comments are fetched, grouped and drafted into a digest, approved, then posted back to Miro.
Miro health
Refreshed 4 minutes ago · every 15 minutes · from the boards collection
Boards
1,284 ↓ 12%
Comments
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Boards created
Last 14 days
By team
Share of activity
Design 34%
Product 27%
Marketing 21%
Research 18%
Collections and dashboards
Miro board health, computed without a model.
Boards created over 14 days, broken down by team, refreshed on a schedule.
Why connect Miro's MCP server through Elaichi
Miro builds and runs this MCP server. Elaichi sits in front of it, so Miro's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Miro's server directly, outside Elaichi, get none of this.
-
One address for every AI client
Claude, ChatGPT, Cursor and Microsoft Copilot reach Miro's tools at the same Elaichi address as every other connected app. Nobody adds Miro's server to each client one by one.
-
Each person signs in as themselves
Each person signs in to Elaichi as themselves. Members connect with their own Miro sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.
-
Rules checked before a call leaves
Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Miro's server. By default, a tool Miro does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.
-
One audit log for every app
Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.
-
Tool issues go to Miro
Miro builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Miro team.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Miro
All three can connect Miro 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 tools | Allow or restrict single Miro 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 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 tools for your AI agents
20 tools are ready to call through Elaichi's MCP endpoint the moment you connect Miro, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Miro builds and runs these tools.
No tools match your search.
Questions, answered
How do I connect Miro to Claude?
Connect Miro in Elaichi first. Miro opens its own sign-in page, you approve access, and 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. Claude signs you in to Elaichi and your Miro boards are available.
Does Miro work with ChatGPT and Cursor as well as Claude?
Yes. Miro 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 extra to set up per client.
What can an AI agent actually do with my Miro data?
Through the Miro connector an agent can search your boards, create a new board, read what is drawn on a canvas and update it, add images, list and sync rows in a table, read and create prototypes, and list, reply to and resolve comments. Short concrete asks work best, such as the name of a board and what you want done on it.
Does connecting Miro give the AI access to every board in my workspace?
No. Every call to Miro runs inside the access of the person who signed in, so the agent sees the boards that person can already open in Miro and nothing more. Elaichi can narrow that further with restrictions, and it never widens it.
Can I stop an agent from changing or deleting things in Miro?
Yes. Restrictions in Elaichi apply per action, so you can allow searching boards and reading comments while restricting canvas updates or new boards. A restricted Miro action still appears in Elaichi's tool search, flagged as restricted, but the AI client cannot run it, whatever the prompt says.
What happens to a Miro connection when someone leaves?
Offboarding a person in Elaichi ends their access to Miro at once. A Miro connection shared with a team keeps working for everyone else. Disconnecting Miro once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.
Does the Miro MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Miro 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?
Yes. Both let Claude, ChatGPT or Cursor use Miro. 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 call.
How is Elaichi different from Composio for Miro?
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: 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 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