miro-board
vv2by nexaedge · author: Jaison Erick
Read any Miro board you can open in your browser, then work out what it says. Miro's public API cannot reach a board you were invited to in someone else's team, and the canvas is WebAssembly so there is nothing in the page to scrape; this reads the board through your own signed-in session instead, opening Chrome once and then talking to Miro's realtime gateway directly. Extraction and interpretation are kept apart on purpose: the scripts measure geometry, colour, containment and edge alignment and never conclude anything, offering overlapping candidate groupings with the evidence behind each, because what a board means lives in how it was arranged and only reading the text can settle it.
What miro-board does, in the publisher's words
Reads a Miro board through your own browser session, and helps an agent say what is on it.
Miro's public API is bound to a pair of user and team, and the app has to be installed on the team that owns the board. A board you were invited to in a client's workspace answers 404 no matter that you can open it in a tab. The page is no help either: Miro renders the canvas in WebAssembly and WebGL, so the content never enters the DOM and there is nothing to scrape. The one path that matches "any board I can open" is the session the browser already holds.
From the project README, punctuation lightly normalized · Open the README on GitHub
- Skills
- 1
- MCP servers
- 0
- Stars
- 1
- License
- n/a
- Repo created
- 2026-03-05
- Last pushed
- 2026-10-01
- Publisher type
- Organization
- Version
- v2
Links
Skills · 1
- miro-board
- Read and interpret any Miro board the user can open, without the Miro API or an installed app. Use when asked what a board contains, to summarise or explain one, to pull its flow, groupings or notes into text, or to answer questions about a board from its URL.
Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.
Category
Integrations & APIs. Assigned by this directory. Agent Plugins 1.0.0 has no category field, so no manifest declares one.
Keywords
miro · whiteboard · board · diagram · extraction
Related by publisher and keywords
Publish a self-contained HTML file as a shareable artifact on artifacts.nexaedge.com. Sign in with any Google Workspace account: the artifact belongs to that account's domain, and only that domain can open it. Also issues expiring links for people outside the domain.
Manage Cloudflare DNS zones and records through Terraform in the nexaedge/infrastructure repository. Automates the full workflow: edit Terraform files, open PR, review plan, merge, watch apply, and verify.
Turn finished analysis results into a self-contained interactive HTML report: charts, cohort heatmaps, sortable tables and stat tiles, all inline in one file that opens by double-click with no network. Carries no brand of its own: it derives a theme from a brand color, or lifts one verbatim out of a report it built earlier.
Spec-driven project execution pipeline backed by Linear. Same skills and agents as spec-plugin, but writes specs, stories and validation to Linear via GraphQL while keeping reasoning artifacts on disk.
Front end for the nexaedge marketplace that works the same on Claude Code, Codex and Antigravity. Detects which agent is running, translates to that agent's native install path, and keeps everything at user scope so a plugin is installed once per machine rather than copied into each repository.
Turn Plaud.ai voice recordings into text inside the repository you are working in: find the recording, transcribe it, bring the transcript down with the speakers it recognises already named. Where that transcript then gets filed is read from the repository's own.plaud.json, never assumed, so the same skill serves a knowledge base and a client project without knowing either.
[](https://agentpluginsdirectory.com/plugins/miro-board)✓ Verified . We fetched the manifest from GitHub and checked it against the official Agent Plugins 1.0.0 schema at agent-plugins.org.