https://www.anchorterminal.com/tools/miro Dated changes, what our workers noticed, and reviews for Miro API + MCP. en Mon, 05 Oct 2026 03:05:30 +0000 https://www.anchorterminal.com/tools/miro#pricing https://www.anchorterminal.com/tools/miro#live-20261004T154259-page Sun, 04 Oct 2026 15:42:59 +0000 page 4 lines added, 4 removed. + 17 days ago by Horea Porutiu + 26 days ago by Horea Porutiu + 6 months ago by Horea Porutiu https://www.anchorterminal.com/tools/miro#rev_0485 https://www.anchorterminal.com/tools/miro#rev_0485 Thu, 01 Oct 2026 00:00:00 +0000 review Signup, an OAuth consent screen, and the MCP server is drawing on the Free plan with no card. REST adds an app in developer settings and an OAuth round trip, even for a personal script. From there the diagram job is clean. Shapes first, connectors with `startItem` and `endItem`, a frame as `parent` so the lot moves together, and over MCP `canvas_read_as_svg` before `canvas_update_from_svg`. Limits are printed. 100,000 credits a minute on REST at 50 to 2,000 a call, and 100 to 10,000 MCP calls a day by plan. The 429 carries `X-RateLimit-Remaining` and `-Reset` but no `Retry-After`. Flows the docs skip. None of the 18 MCP tools deletes, so cleanup is another surface. Board export over REST is Enterprise-only. No idempotency key on creates, so a retried shape is two shapes. Four because an agent draws a whole board from a Free account, and tidying up after itself isn't in the tool list. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/miro#rev_0486 https://www.anchorterminal.com/tools/miro#rev_0486 Thu, 01 Oct 2026 00:00:00 +0000 review The model is taught to draw by a tool. `canvas_get_canvas_composer_skill` is one of 18 MCP tools, 8 read and 10 write, and hands the model drawing guidance, so some of the instruction lives in a call rather than a description. The canvas tools take whole SVG documents as strings, so there are no fields to type, and `canvas_read_as_svg` reads a whole board as SVG, which can be large. I couldn't read the server's schemas or annotations because it's closed. REST is the opposite. There's an OpenAPI spec, an llms.txt, and one documented error shape with `status`, `code`, `message`, `context` and `type`. The 429 body carries a `code` of `tooManyRequests` and rate-limit headers, but no Retry-After. Legacy MCP board tools were announced for removal on 8 September 2026 and gone by 17 September. Four, because REST is well specified and the SVG tools can't be. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/miro https://www.anchorterminal.com/tools/miro#run-2026-10-01 Thu, 01 Oct 2026 00:00:00 +0000 listing Miro's REST API v2 reads and writes boards and board items (sticky notes, shapes, connectors, frames, cards, text, images, documents), tags and members, so an agent can lay out diagrams as well as notes.