Miro
Miro is a collaborative online whiteboard enabling teams to brainstorm ideas, design wireframes, plan workflows, and manage projects visually
Verdict
Common use cases
- Prototype user flows during design reviews
- Generate sprint boards from meeting notes
- Archive completed project boards from chat
- Pull board member lists for access audits
- Push app cards with custom metadata fields
Integration
- Vendor
- Miro
- Category
- other
- Auth
- OAUTH2
- Tools
- 14
- Composio slug
miro
Tools
- Create App Card Item
Tool to add an app card item to a board. use when you need to push a rich preview card with custom fields into a miro board (e.g., after assembling card data).
- Create Board
Tool to create a new board. use when you need to set up a board with a specific name, description, and policies. example: "create a new board named project plan".
- Delete App Card Itemdestructive
Tool to delete an app card item from a board. use when you need to remove an app card item created by your app after it is no longer needed.
- Delete Document Itemdestructive
Tool to delete a document item from a board. use when you need to remove a document item (e.g., pdf or image) that is no longer relevant. example: "delete the document item with id 'item456' from board 'board123'."
- Delete Itemdestructive
Tool to delete a specific item from a board. use when you need to remove an item (e.g., shape, sticky note) after confirming its board and item ids.
- Get App Card Item
Tool to retrieve a specific app card item by its id. use when you need the details of an existing app card item.
- Get Board
Tool to retrieve details of a specific board. use when you have a board id and need to fetch its metadata.
- Get Board Members
Tool to retrieve a list of members for a board. use when you need to list all users with access to a board after confirming its id.
- Get Boards
Tool to retrieve accessible boards with optional filters. use when you need to list or search boards by team, project, owner, or keywords.
- Get Connectors
Tool to retrieve a list of connectors on a board. use after confirming the board id and when you need to page through connector items.
- Get Tag
Tool to retrieve details of a specific tag on a board. use when you have a board id and tag id and need its metadata.
- List Organizations
Tool to retrieve list of organizations accessible to the user. use when you need to view all available organizations.
- Update App Card Item
Tool to update an app card item on a board. use when you need to modify properties of an existing app card item. include only fields to change.
- Update Board
Tool to update properties of a specific board. use when you have a board id and need to modify its name, description, or permissions policy. use after confirming the board exists.
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations. 2. Find Miro in the list and click Connect. 3. You'll be redirected to Miro's OAuth consent screen — sign in with your Miro account. 4. Grant the requested scopes: boards:read and boards:write (these let Switchy create boards, add items, and fetch member lists). 5. After authorizing, you'll return to Switchy and see a green Connected badge next to Miro. 6. To test, open any Space and type '@Miro create a board named Test Board' — the MCP should reply with a confirmation and a board link. 7. Click the link to verify the board exists in your Miro workspace. 8. To invoke other tools, use '@Miro' followed by your request (e.g., '@Miro add a sticky note to board abc123 with text Prototype idea').
What teammates see: by default, memories from Miro are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Create Sprint Board
@Miro create a board named 'Q2 Sprint Planning' with description 'Roadmap and backlog for April-June sprint cycles'Open in a Space →
Add Sticky Note
@Miro add a sticky note to board 12345 with text 'User feedback: simplify onboarding flow'Open in a Space →
Fetch Board Members
@Miro get the list of members for board 67890Open in a Space →
Push App Card
@Miro create an app card on board 11223 with title 'Design System Audit' and fields status: in-progress, owner: alexOpen in a Space →
Delete Old Item
@Miro delete item item456 from board 33445Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@miro show me all the members who have access to our Q1 Planning board and their roles
Here are the 8 members with access to your Q1 Planning board: • Sarah Chen (Owner) – full edit and admin rights • Marcus Rodriguez (Editor) – can edit all content • Priya Sharma (Editor) – can edit all content • Tom Wilson (Commenter) – can comment but not edit • Lisa Park (Viewer) – view-only access • James Kumar (Editor) – can edit all content • Emma Thompson (Commenter) – can comment but not edit • Alex Martinez (Viewer) – view-only access This snapshot reflects current board permissions. Note that board owners can modify access at any time.
This example demonstrates read-only board introspection — useful for auditing who can see sensitive planning work. Requires OAuth scope to read board membership. The MCP returns current state only; it won't notify you of future permission changes.
@miro create a new board called 'Customer Journey Map Workshop' with description 'Mapping touchpoints for Q2 product release' and set it to team-editable
Created board 'Customer Journey Map Workshop' successfully. Board ID: 3458764513924587136 Direct link: https://miro.com/app/board/3458764513924587136/ Description set to: 'Mapping touchpoints for Q2 product release' Sharing policy: Team members can edit (anyone with the link can view) The board is empty and ready for content. You can now add sticky notes, shapes, or app cards using additional commands, or open the link to work visually in Miro.
This write action creates a persistent artifact in your Miro workspace. The board remains after the prompt completes — you're responsible for cleanup if it was a test. Requires OAuth scope to create boards. Sharing policies depend on your team's Miro plan tier.
@miro pull the latest app card items from our 'Sprint Retrospective' board and summarize the top 3 themes from the feedback
Retrieved 17 app card items from your Sprint Retrospective board. Here are the top 3 recurring themes: 1. **Deployment friction** (6 mentions) – Teams cited slow CI/CD pipelines and unclear rollback procedures as blockers. Cards reference specific incidents on Feb 12 and Feb 19. 2. **Cross-team communication gaps** (5 mentions) – Design and engineering noted misaligned expectations on feature scope. Several cards suggest weekly sync meetings. 3. **Testing coverage concerns** (4 mentions) – QA flagged missing edge-case tests for the payment flow. Cards link to Jira tickets QA-441 and QA-448. This synthesis is based on card titles and custom field text visible to the MCP at retrieval time.
This example pairs Miro's data retrieval with AI reasoning to surface patterns humans might miss in a crowded board. The MCP sees card metadata and custom fields, but can't parse embedded images or freeform drawings. Best for structured retrospective formats.
Use-case deep-dives
When Miro beats shared docs for distributed design work
A 6-person design team runs a 3-day remote sprint and needs to consolidate research findings, sketches, and voting results in one place. This MCP wins when your AI needs to programmatically push structured data (user quotes, feature cards, prioritization scores) onto a Miro board without manual copy-paste. The Create App Card Item tool lets you turn interview transcripts or analytics summaries into rich preview cards that designers can cluster and vote on. The trade-off: OAuth2 setup takes 20 minutes and you need a Miro paid plan for API access. If your team already lives in Miro and runs sprints monthly, the MCP pays for itself by eliminating the "someone paste the research into the board" bottleneck. If you run sprints quarterly or your team prefers Figma, skip it.
How this MCP automates pre-workshop board setup
A 3-person consulting team runs weekly client workshops and spends 30 minutes before each session creating a Miro board with agenda, icebreaker prompts, and pre-populated sticky notes. This MCP is the right call when you have a repeatable workshop format and want your AI to scaffold boards from a template or CRM data. The Create Board tool sets up the board with the right permissions, then you can push agenda items or client-specific context cards programmatically. The boundary: if your workshops vary wildly in structure or you only run them twice a quarter, the OAuth setup overhead outweighs the time saved. This wins for teams running 8+ workshops a month with consistent formats. If you're a solo consultant or your workshops are one-offs, a manual Miro template is faster.
When Miro isn't the right tool for task follow-through
A 5-person product team wants to extract action items from a Miro retrospective board and push them into Linear or Asana. This MCP doesn't help here—it has no read tools for sticky notes or text items, only for app cards and documents. You can delete items or fetch board metadata, but you can't parse the retro content your team actually wrote. The Get Board Members tool is useful for tagging the right people, but without a way to read sticky note text, you're stuck manually copying tasks out. If your workflow is "brainstorm in Miro, execute in a project tool," you need a different integration (or manual export). This MCP is for pushing data into Miro, not pulling insights out. Save your OAuth setup time unless you're automating board creation or card publishing.
Frequently asked
What can Switchy's Miro MCP do with my boards?
It creates and deletes boards, adds or removes items (sticky notes, shapes, documents, app cards), and reads board metadata and member lists. Think of it as programmatic access to the core Miro canvas — your AI can assemble a board structure, push content cards, or clean up items without opening the Miro UI.
Does the Miro MCP need admin access to my workspace?
No. OAuth2 scopes are granted per-user, not workspace-wide. The connected user needs edit access to the boards the MCP will modify, but they don't need Miro admin privileges. If your team restricts board creation, the MCP won't bypass that policy.
Can it read or edit existing sticky notes and shapes?
It can delete items by ID, but the tool list shows no "update sticky note" or "read shape content" methods. If you need to modify existing canvas objects in place, you'll hit the Miro REST API directly or use a different integration. The MCP focuses on creation and removal.
Why use this instead of Miro's Zapier or Make integrations?
Those trigger on events (new board, item moved) and push data elsewhere. Switchy's MCP lets your AI decide in real time which board to create, what cards to add, and when to delete items — all inside a conversational workflow. Use Zapier for automation pipelines; use the MCP for AI-driven board assembly.
Who on the team should connect the Miro account?
Whoever owns the boards your AI will touch. If the MCP creates boards under their name, they'll appear as the owner in Miro's audit log. For shared team boards, connect a service account or a user with consistent access so the integration doesn't break when someone leaves.