Official Miro AI developer tools and integrations. Includes MCP server configuration, Claude Code skills, and resources for building AI-powered experiences with Miro boards.
Skill Claude CodeCodex
Documentation architecture for this repository. Use when creating, updating, or reviewing README.md, CONTRIBUTING.md, or docs/ files. Covers separation of concerns, vendor documentation standards, cross-references, and validation.
Skill Claude CodeCodex
Use when authoring or revising plugin SKILL.md files in this repo. Captures the principles for keeping skills as compact shortcuts to MCP tool groups.
Skill Claude CodeCodex
Part of miro
Use when the user wants to explore, list, summarize, or inspect items on a Miro board.
Skill Claude CodeCodex
Part of miro
Use when the user wants to explain or visualize a codebase on a Miro board — produces a minimal, notation-correct set of architecture / structure / behavior diagrams (flowchart, UML class, UML sequence, ERD) plus a short companion document, grounded in real repo artifacts.
Skill Claude CodeCodex
Part of miro
Use when the user wants to create a visual code review on a Miro board from a pull/merge request (GitHub, GitLab, or any forge), local uncommitted changes, or a branch comparison — produces a file-changes table, summary/architecture/security docs, and architecture diagrams, then links them back from the PR/MR.
Skill Claude CodeCodex
Part of miro
Use when the user wants to extract a Miro board's specs (documents, diagrams, prototypes, tables, frames, images) to local .miro/specs/ files for AI-assisted planning and implementation — accepts a board URL or single-item URL.
Skill Claude CodeCodex
Part of miro
Use when the user wants to create or update a diagram on a Miro board.
Skill Claude CodeCodex
Part of miro
Use when the user wants to create or edit a Google-Docs-style markdown document on a Miro board.
Skill Claude CodeCodex
Part of miro
Use when the user wants to create or update a structured table on a Miro board.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: