Miro MCP

Miro MCP wraps the official Miro SDK so you can create boards, add sticky notes, and manipulate whiteboard items from Claude. It's the kind of tool that sounds niche until you're three hours into a remote workshop and realise you've been manually transcribing ideas into Miro while everyone waits. I've used it to spin up retrospective boards mid-conversation, drop sticky notes into swim lanes, and prep workshop canvases before a session even starts. The server handles authentication via a personal access token, which you generate from Miro's developer portal. Once connected, you can ask Claude to scaffold a board structure, populate it with content from a discussion, or even reorganise items based on themes. The SDK coverage is solid: boards, frames, sticky notes, shapes, connectors. It doesn't expose every Miro feature, but it hits the collaboration workflows that matter. One quirk: you're working with the REST API under the hood, so batch operations can feel a bit chatty. If you're trying to create 50 sticky notes at once, expect some latency. The other thing to watch is that Miro's permissions model carries over. If your token doesn't have write access to a board, the server will fail gracefully, but you won't know until you try. I'd reach for this when I'm facilitating remote sessions and want to offload the busywork of board setup, or when I'm synthesising conversation threads into visual artefacts without context-switching. If you're a solo user who occasionally opens Miro to sketch an idea, this is overkill. But if you're running workshops, design sprints, or async brainstorms where the board is the artefact, it's a genuine time-saver. The community status means it's maintained by one developer, so expect slower updates than official servers, but the codebase is clean and the SDK wrapper is straightforward.