01 · Records and state owned
Boards, frames, sticky notes, shapes, text, cards, documents, tables, images, diagrams, prototypes, layouts, board items, and comment threads.
Miro
Miro
Miro is included for a hosted MCP that lets authorized users search, summarize, create, and update boards, visual structures, documents, tables, images, prototypes, and comment threads from compatible AI clients.
Content, CMS, creative & DAMSystem of productionBYO-UI-ready platform
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Search accessible boards; summarize board or item context; list board items and comments; inspect layouts, diagrams, documents, tables, prototypes, and image download links.
03 · Actions and write paths
Create boards, layouts, diagrams, documents, tables, prototypes, code widgets, images, and board items; update layouts, documents, tables, or widgets; reply to comments and resolve or reopen threads.
04 · Authentication and permissions
The hosted server uses OAuth 2.1 with dynamic client registration and acts within the authenticated user's current board permissions. Enterprise administrators control organization and selected-team availability.
05 · Monitoring, approval, and recovery
Respect current board and team access, preview the target board and affected visual region, and confirm bulk layout changes, prototype creation, comment resolution, or overwrites to documents and tables before execution.
06 · Limits and caveats
Official plan language conflicts: the main MCP page says Enterprise Plan Only, while the FAQ and usage guide say MCP is available across plans with plan-based daily call allowances. Enterprise use requires administrator enablement; calls stop when the daily allowance is exhausted.
Agent access
MCP support
Official MCP serverMiro-hosted remote MCPCurrent hosted service; plan eligibility unresolved because official documentation conflicts
Support: Official MCP server
Read scope: Search boards and read board context, item structure, comments, layouts, documents, tables, prototypes, diagrams, and image links available to the connected user.
Write scope: Create boards and visual structures; add or update items, documents, tables, images, diagrams, prototypes, and code widgets; reply to comments and change comment resolution state.
Authentication: OAuth 2.1 with dynamic client registration connects a compatible client to Miro's hosted endpoint and a selected team.
Approval boundary: Confirm the target team and board plus the affected frames, items, documents, tables, prototypes, and comment threads before state-changing calls, especially generated multi-item layouts.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access4
Identity4
Governance4
Agent access3
UI extensibility4
Portability4
Observability3
Documentation5
Proposed customer-shaped experiences
What customers could create on top.
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Miro ships them.
Single-platform patterns
- Campaign planning, journey mapping, and visual launch room
- Campaign asset assembly room
- Brief-to-experience studio
- Content approval queue
Multi-platform compositions
- Miro + CRM or campaign platform: campaign asset assembly room
- Miro + work-management system + analytics or distribution platform: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
5 recorded sources
MCPRepresentative source
https://developers.miro.com/docs/miro-mcp ↗Official Miro developer documentation confirms a remote OAuth server in Public Beta. Enterprise organizations must enable it; some expanded creation/workflow tools have plan-specific availability, so profiles must…
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
APISource inventory
https://developers.miro.com/reference/ ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Developer docsSource inventory
https://developers.miro.com/ ↗First-party developer documentation or platform overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
HomepageSource inventory
https://miro.com/ ↗First-party product homepage used to confirm product identity and current positioning.
- Publisher published
- Jul 10, 2026
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Release notesSource inventory
https://developers.miro.com/changelog/removed-experimental-webhooks-support ↗Reverified a retired or moved source and preserved its capability/date boundary.
- Publisher published
- Dec 5, 2025
- BYO-UI reviewed
- Jul 12, 2026
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
Verified fact
Tied to cited first-party evidence reviewed for this profile.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.