Your use of the Miro MCP Server Beta is subject to Section 16 (Trial and Beta Access) of Miro’s Master Cloud Agreement, or similar Beta provision in the agreement applicable between you and Miro. Some of the setup and functionality of Miro MCP Server may change throughout the Beta. Please review our MCP documentation or access our Help Center carefully.
Miro MCP Server
Miro’s MCP Server, when connected and authorized by a user, allows a third-party AI Agent to interact with content on Miro boards that the authorized user has access to.
Our MCP Server has a set of tools that allow the AI Agent to read and write content on selected Miro boards. Miro MCPs current design requires that users need to be explicit with which boards the third party AI Agent should be reviewing. The AI Agent will not be able to discover or read boards that the user hasn’t included in their prompts. Should this change in future iterations of Miro MCP, our documentation will be updated to reflect it.
Managing Miro MCP Server in your organization
Once you have been approved for Miro’s MCP Server Beta, Miro will whitelist your Organization for access to MCP.
This Beta feature may contain bugs, errors, or other stability issues. Miro makes no commitments, representations, or warranties regarding the performance, availability, or fitness for any particular purpose. Miro’s service levels, security obligations, support obligations, and indemnities under the MCA (or other service agreement) do not apply.
Implementing Miro MCP into your organization requires an Administrator to install the Custom MCP App Access our documentation to see here how to install an App. When installing the App into your Miro environment, it’s important to consider how users within your organization can interact with the App. You can:
- Enable the App for the entire Organization: This means any user within your Organization can choose to access, connect and start using MCP with boards that they have access to. All Miro boards in your Organization may potentially be accessed via Miro MCP. Users will be able to prompt using boards in your Organization and will receive errors for boards that are inside separate organizations, unless they are made public. More information on board settings here.
- Enable the App for specific Teams: If you enable Miro MCP only on a specific Team, only the users in that Team will be able to access and connect to Miro MCP. All Miro boards in your specific Team may potentially be accessed via Miro MCP.. More information on board settings here.
Authorizing Miro MCP Server as a user
Once Miro has been enabled for your Organization or for a specific Team, users will be able to connect to Miro MCP.
- Users can follow the detailed instructions for the different tools in our documentation.
- Once a user has added Miro MCP to their tool of choice, they’ll be prompted to follow a standard OAuth 2.1 flow for MCP Servers.
- Users will need to select a Team they are a member of that has had the Miro MCP App enabled. It is important that Administrators have authorized Miro MCP for the selected Team.
- Once authorized, the user will be redirected back to their third party tool and can check to make sure the connection is completed, by accessing and viewing the Miro MCP Tools.
- Users will then be able to prompt their AI Agent to access the Tools in Miro’s MCP Server to perform actions on their behalf. These prompts must contain the Board URL for the AI Agent to understand which board it should be accessing, via the MCP Server. These prompts and the results are dictated by the end user and the LLM being the AI Agent respectively, not Miro.
- Actions performed by the AI Agent with Miro MCP Server include:
- Accessing and summarizing Board data
- Creating Miro Formats
- As Miro moves its MCP Server into Public Beta and General Availability, we may include additional Tools, allowing more actions to be done by the AI Agent.
- Actions performed by the AI Agent with Miro MCP Server include:
Considerations
Miro’s MCP tool was built following the standards outlined on Anthropic’s MCP documentation. According to the MCP Server Standards all data being sent to the MCP Server is being prepared by the MCP Client on the users side. Most modern tools allow the preview of data before it's being sent to the remote MCP Server and provide explicit grant for the tool-calling.
This is a Beta feature and we will be making improvements throughout the Beta to our MCP Server and the Tools that are available to customers. We will do our best to proactively update Beta customers and will keep our documentation up to date for what is available in our MCP Server.
Miro MCP Server Tools
Tools are the actions that help an AI Agent interact with Miro. Certain tools inside Miro’s MCP Server will leverage Miro AI for better results, see table below. Here is the list of current Tools available and what they are used for. Check out our documentation for a list of tools as this list will change over time.
| Tool name | Description | Uses Miro AI credits |
|---|---|---|
| board_get_items | Find specific items on a board | No |
| board_get_image_download_url | Download images from board | No |
| board_get_image_data | Find images on a board | No |
| context_get_board_docs | Summarize a board's information | Yes |
| draft_diagram_new | Create a new Diagram on a selected Miro Board | Yes |