Loading...

An MCP server that connects to Miro Whiteboard, enabling board manipulation, sticky note creation, and bulk operations via OAuth authentication.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
An MCP server that connects to Miro Whiteboard, enabling board manipulation, sticky note creation, and bulk operations via OAuth authentication.
This server allows for both read and write operations on Miro boards, making it moderately risky. The use of OAuth provides some security, but careful management of the token and awareness of the potential impact of bulk operations are essential.
Performance depends on the size of the Miro board and the complexity of the operations being performed. Bulk operations may take longer to complete.
Consider the cost of Miro API calls, especially for large boards or frequent operations.
npx -y @smithery/cli install @llmindset/mcp-miro --client claude{
"mcpServers": {
"mcp-miro": {
"command": "/path/to/node-or-npx",
"arguments": [
"/path/to/mcp-miro/build/index.js",
"--token","MIRO-OAUTH-KEY"
]
}
}
}Get Board ContentsRetrieves the contents of a specified Miro board.
Read-only operation; no modification of the board.
Create StickyCreates a new sticky note on a Miro board.
Adds content to the board; non-destructive.
Create ShapeCreates a new shape on a Miro board.
Adds content to the board; non-destructive.
Read BoardReads the metadata and structure of a Miro board.
Read-only operation; no modification of the board.
Read FrameReads the contents of a specific frame within a Miro board.
Read-only operation; no modification of the board.
Read ContentsReads the contents of a specific object on a Miro board.
Read-only operation; no modification of the board.
Bulk CreateCreates multiple objects (e.g., sticky notes, shapes) on a Miro board in a single operation.
Adds content to the board; non-destructive but can significantly alter the board state.
OAuth
local
This server allows for both read and write operations on Miro boards, making it moderately risky. The use of OAuth provides some security, but careful management of the token and awareness of the potential impact of bulk operations are essential.
The level of autonomy depends on the specific tools used and the permissions granted to the OAuth token. Exercise caution when using write operations.
Production Tip
Monitor Miro API usage to avoid rate limiting and ensure stable performance.
You need to create a Miro app and obtain an OAuth token through the Miro developer platform.
The server will no longer be able to access the Miro API. You will need to refresh or re-authenticate to obtain a new token.
Yes, as long as the OAuth token has the necessary permissions for each board.
Use the MCP Inspector to monitor communication between the client and the server.
No, this server primarily focuses on programmatic board manipulation, not real-time interaction.
The number of objects you can create in a single bulk operation may be limited by the Miro API. Monitor API usage to avoid rate limiting.
There is no built-in rollback support. You may need to manually revert changes or implement your own versioning system.