Miro
Let your coding agent read and update Miro boards while you plan features, map user flows, or sync workshop notes without leaving the terminal.
Overview
ai.waystation/miro is an MCP server for the Build phase that connects your agent to Miro boards for visual collaboration and planning.
What is this MCP server?
- Remote MCP via Waystation with streamable-http and SSE endpoints (v0.3.1)
- Miro integration for team visual boards from Claude Code, Cursor, or Codex
- Supports collaboration workflows: diagrams, retros, and product maps in one hosted bridge
- No local Miro SDK install—register the remote server URL in your MCP client
- Pairs with planning-heavy stacks where specs live on canvas before tickets in GitHub
- Server version 0.3.1 per MCP manifest
- 2 remote transports: streamable-http and SSE
- Hosted endpoints on waystation.ai/miro/mcp
Community signal: 54 GitHub stars.
What problem does it solve?
Your product map and agent chat live in different tools, so you keep copy-pasting context off Miro boards into prompts.
Who is it for?
Indie builders who already run roadmaps or architecture diagrams in Miro and want Claude or Cursor to reference and update them during implementation.
Skip if: Teams that need deep Miro REST automation with custom enterprise governance and no third-party hosted MCP proxy.
What do I get? / Deliverables
After you add the Waystation Miro MCP remote, your agent can work against live boards so diagrams and plans stay the single source of truth.
- Live Miro board context available inside agent sessions
- Agent-driven updates and summaries aligned to your visual boards
- Reduced manual export of diagrams into chat prompts
Recommended MCP Servers
Journey fit
Visual boards sit on the Build shelf because indie builders most often wire Miro into agent workflows for roadmaps, architecture sketches, and sprint boards during active product work. PM is the canonical subphase: Miro is a work-management surface for items, timelines, and diagrams—not a code editor or deploy target.
How it compares
Hosted Miro MCP bridge, not a local skill that only describes how to use Miro manually.
Common Questions / FAQ
Who is ai.waystation/miro for?
Solo builders and small teams using Miro for planning who want their AI coding agent to read and act on board content through MCP.
When should I use ai.waystation/miro?
Use it when scoping features, maintaining roadmaps, or syncing workshop output on Miro while you code with Claude Code, Cursor, or Codex.
How do I add ai.waystation/miro to my agent?
Add the remote MCP URL https://waystation.ai/miro/mcp (streamable-http) or the SSE URL https://waystation.ai/miro/mcp/sse in your client’s MCP settings and complete Waystation’s Miro authorization.