Miro MCP connector
Connect Miro to Elaichi and Claude, ChatGPT, Cursor or any MCP client can search boards, read and reply to comments, update canvases and pull table rows as the person who signed in.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
20 tools
How to connect
How to connect Miro to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Miro once
-
Open Connections, choose Add connection, and pick Miro.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Miro. Miro's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
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 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 today. 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.
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.
Use cases
What teams do with Miro through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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”
Compare
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 | $15 per user per month. | 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.
AI tools
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.
See it in Elaichi
What connecting Miro gets you
6 screens from the product, each doing one job for your Miro account.
The agent
Ask about Miro boards in plain language.
Search boards, read comments and pull table rows by asking the Elaichi agent.
- boards
- comments
- tables
- prototypes
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 or Cursor
MCP clients
Use Miro from Claude, ChatGPT or Cursor.
One governed endpoint, connected once over OAuth, with no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
20 Miro tools, ready without writing code.
Boards, canvases, comments, tables, images and prototypes, covered with no custom code.
- Image get data
- Image get upload URL
- Image get URL
- Table create
ElaichiToolsToolboxes
Every team gets its own Miro toolbox.
Design, product and marketing each see the Miro tools their work needs.
- Design
- Product
- Marketing
- Research
ElaichiToolboxesShared connections
Share one Miro connection without sharing credentials.
Teammates work through the Miro account one person connected, never seeing a credential.
- Design
- Product
- Marketing
- Research
ElaichiConnectionsAudit log
Every Miro action is logged with a name.
See who created a board, replied to a comment or changed a canvas, and when.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
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 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 Michael Brennan
Approve Deny -
Post the digest
Miro
Queued
Collections and dashboards
Miro board health, computed without a model.
Boards created over 14 days, broken down by team, refreshed on a schedule.
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%
Related connectors
More from the catalog
FAQ
Frequently asked questions
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, 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 blocking canvas updates or new boards. A restricted Miro action is never advertised to the AI client, so no prompt can reach it.
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 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, 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 on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.