# 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. Source: https://elaichi.ai/connectors/miro/ ## Facts | | | | --- | --- | | Application | Miro | | Category | Design | | AI tools | 20 | | Authentication | Connects over OAuth | | Bring your own OAuth app | No | | Native MCP | Yes. Miro builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top | | Support for its tools | help.miro.com/hc/en-us | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, 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 is connected - 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 ## Connect Miro in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Miro. 2. Optionally set Share with, then press Connect. 3. Approve it in Miro. Miro's own window opens. Whoever approves it decides what this connection can reach. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Miro tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Miro 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 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 today. The plugin directory lives at chatgpt.com/plugins. ## Miro 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. ## Connect Miro 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 Only Read is granted by default, which is not enough to call a Miro tool. 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. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Miro through Elaichi ### Turn a review into resolved comments Design. 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. ### Find the board from last quarter's kickoff Product. 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. ### Spin up a campaign planning board Marketing. 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. ### Keep a findings table in step Research. 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. ### Read a prototype before the standup Engineering. 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. ### Close out a workshop board Operations. 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. ## 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. 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 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](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 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 my team share one Miro connection? Yes. One person connects Miro in Elaichi and shares the connection with a team, and nobody else ever handles a credential. Each teammate still signs in to Elaichi as themselves, so the audit log names the person behind every board, comment or canvas change. ### 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. ## All 20 Miro tools Every tool below is callable through https://api.elaichi.ai/mcp once Miro is connected, subject to the toolbox it is in and the restrictions on the caller. - **Image get data** (Get). Get image metadata and base64-encoded image data for an image item on a Miro board. - **Image get upload URL** (Get). Get a temporary, single-use presigned POST URL for uploading an image. - **Image get URL** (Get). Get a download URL for an image item from a Miro board. - **Table create** (Create). Create a table on a Miro board with specified columns. - **Table list rows** (List). Get rows from a Miro table with column metadata and optional filtering. - **Table sync rows** (Sync). Add or update rows in a Miro table using key-based upsert matching. - **Board create** (Create). Create a new Miro board. - **Board search boards** (Search). Search and list boards accessible to the current user. - **Comment list comments** (List). List comments from a Miro board or a specific item on the board. - **Comment reply** (Reply). Add a reply to an existing comment thread on a Miro board. - **Comment resolve** (Action). Resolve or unresolve a comment thread on a Miro board. - **Image create** (Create). Create an image item on a Miro board. - **Canvas create from svg** (Create). Create multiple board items on a Miro board from SVG. - **Canvas get canvas composer skill** (Get). Get the SVG format specification for creating board layouts. - **Canvas read as svg** (Action). Read existing board items and return them as SVG. - **Canvas update from svg** (Update). Apply an SVG document as a diff. - **Prototype read** (Action). Read prototype screens from a Miro board, including metadata - **Prototype create** (Create). Create a Miro prototype from one or more HTML screens, using either uploaded HTML tokens (preferred) or inline HTML contents. - **Canvas load format skill** (Action). Use on top of the base spec for format-specific guidance such as diagramming notation. - **Canvas search** (Search). Find what is on a board before reading it. Supports an overview mode for a high-level pass.