Miro MCP Server – Boards, Diagrams, and Workshops
Miro's official MCP server gives AI agents permission-aware access to Miro boards and supported canvas actions. Use it to understand board content, generate diagrams, create structured workshop materials, work with comments, and turn visual collaboration context into actionable outputs.
Overview
Miro's official hosted MCP server connects compatible AI agents directly to
Miro boards. It gives an agent structured access to live visual-collaboration
context instead of requiring users to manually copy board content into a
prompt. The service is designed for workflows that combine brainstorming,
planning, diagramming, workshops, and team feedback.
What the MCP server enables
Miro documents tools for reading, searching, summarizing, and creating board
content. Depending on the authenticated user's permissions and the enabled
tools, an AI agent can:
- Search, understand, and summarize content on accessible boards.
- Create structured board layouts with frames, sticky notes, shapes, text,
cards, documents, tables, and images from URLs. - Generate architecture, sequence-flow, entity-relationship, and other
supported diagrams. - Read comments, resolve supported comments, and turn feedback into next steps.
- Use board context to help explain code, compare user journeys, prepare
workshops, or support planning activities.
When to use it
Use Miro MCP when an AI workflow needs live visual context or must add
structured content to a Miro board. Practical uses include preparing sprint
planning or retrospective boards, summarizing discovery workshops, generating
diagrams from code or specifications, documenting system architecture,
comparing customer journeys, and converting team discussion into organized
action items.
Connection and authentication
Miro provides a hosted remote MCP endpoint at https://mcp.miro.com/.
Compatible clients connect over Streamable HTTP and complete an OAuth 2.1 flow
with dynamic client registration. During authorization, the user selects the
Miro team that contains the boards they want the agent to access.
No static authorization header or local stdio package is required in Miro's
documented direct configuration. The MCP client must support remote servers
and OAuth 2.1.
Key considerations
Miro MCP is team-specific. A user can be authenticated to only one Miro team at
a time, and re-authenticating to another team replaces the previous connection.
Board access follows the user's existing permissions. Enterprise organizations
must have an administrator enable MCP for the relevant teams before users can
connect. Standard Miro API rate limits apply. Use only one installation method
per client to avoid duplicate tools and conflicting OAuth sessions, and require
human review before making high-impact changes to shared boards.
Supported Transports
streamable_http
URL: https://mcp.miro.com/
Frequently Asked Questions
- When should an AI agent use the Miro MCP server?
- Use it when a workflow needs live Miro board context or supported canvas actions, such as summarizing workshop content, generating diagrams, preparing planning boards, organizing feedback, or turning visual collaboration into documented next steps.
- What does the Miro MCP server add to an AI agent's capabilities?
- It gives the agent structured access to permitted Miro boards and tools for understanding, searching, summarizing, and creating visual content instead of relying only on static model knowledge or manually pasted board text.
- What can an AI agent access or manage through Miro MCP?
- Depending on permissions and available tools, the agent can work with board content such as frames, sticky notes, shapes, text, cards, documents, tables, images, diagrams, and comments. Access remains limited to boards in the currently authorized Miro team.
- How is authentication configured for the Miro MCP server?
- Miro uses OAuth 2.1 with dynamic client registration. The user completes an interactive authorization flow and selects one Miro team. Enterprise users also need an administrator to enable MCP for the relevant organization and teams.
- Which transport should be used for the Miro MCP server?
- Use Streamable HTTP with https://mcp.miro.com/. Miro's documented direct setup uses its hosted remote endpoint with OAuth 2.1; no official local stdio server or static bearer-token configuration is included here.