miro-doc
Create Document on Miro Board
Create a markdown-formatted document on the specified Miro board.
Inputs
Identify from the user's request:
- board-url (required): Miro board URL
- content (optional): Document content or topic to write about
Supported Markdown
The document supports:
# Heading 1through###### Heading 6**bold**and*italic*- unordered listsand1. ordered lists[link text](url)
Not supported: Code blocks, tables, images, horizontal rules.
Workflow
- If board URL is missing, ask the user for it
- If content is provided:
- If it's actual document content, use it directly
- If it's a topic/request, generate appropriate document content
- If content is missing, ask what document they want to create
- Call
doc_createwith the board URL and the markdown content. To place the document inside a frame, pass the board URL with?moveToWidget=<frame_id>— the tool will detect the frame target automatically (noparent_idargument exists). When that URL is used,xandybecome coordinates relative to the frame's top-left corner; pick values that fit inside the frame's width and height (default doc width is 800px). - Report success with a link to the board
Coordinates
- Board-level (URL has no
moveToWidget):x=0, y=0is the board center. - Frame target (URL has
?moveToWidget=<frame_id>):x=0, y=0is the frame's top-left corner. The doc's top-left is placed at the givenx, y, and the doc must fit inside the frame's width and height. Targets that point at a non-frame item (sticky note, shape, diagram) are silently ignored, so the doc lands on the board.
Examples
User input: create a doc on https://miro.com/app/board/abc= with: # Meeting Notes\n\n## Attendees\n- Alice\n- Bob
Action: Create document with the provided markdown content.
User input: make a sprint planning notes template doc on https://miro.com/app/board/abc=
Action: Generate a sprint planning notes template document with appropriate sections.
User input: create a document on https://miro.com/app/board/abc=
Action: Ask the user what document they want to create.
Document Templates
When generating content, consider these common document types:
- Meeting notes - Date, attendees, agenda, action items
- Project brief - Overview, goals, timeline, stakeholders
- Sprint planning - Sprint goal, backlog items, capacity
- Retrospective - What went well, improvements, action items
- Decision log - Context, options, decision, rationale
Editing Existing Documents
To modify a document already on the board:
- Call
doc_getwith the document URL to read its current content and version. - Call
doc_updateto apply find-and-replace edits against that version.
This is the right pattern when the user wants to amend a section or update a list rather than replace the whole doc.
More from miroapp/miro-ai
miro-mcp
>-
235miro-platform
>-
82documentation-structure
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.
69miro-code-review
Knowledge and patterns for effective code review visualization
61miro-spec-guide
>-
49miro-code-spec
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.
3