Miro Mcp Operations

If project-config.json is missing, instruct the user to copy project-config.template.json and fill in values.

Content Requirements

• Keep labels concise and collaboration-friendly.
• Preserve important structure from the source artifact.
• Follow any domain-specific rules provided by the calling workflow.

Validation Steps

1. Confirm Miro MCP connectivity before attempting write operations.
2. Create or update the requested content in Miro.
3. Capture the resulting Miro URL.
4. Update any required tracking artifact specified by the calling workflow.
5. Ensure local source artifacts remain synchronized when required.

Failure Handling

If Miro publication cannot execute:

1. Keep the calling workflow's local source artifacts current.
2. Record blocker status in the calling workflow's tracking artifact and completion summary.
3. Do not claim Miro publication succeeded.

Output Requirements

• Return the Miro board/frame link when available.
• Preserve local source-of-truth artifacts as directed by the calling workflow.
• Record status in the calling workflow's tracking artifact when required.