Miro Workflows

Classification

Built artifact

Repository

Alexi5000/miro-workflows

Language

TypeScript

Licence

MIT

Status

Active development

Tests

3 recorded gates

Last verified

2026-08-01

This is the closest public analogue to an exit from a visual work tool. Board content becomes a real schema with typed relations, an MCP tool surface exposes the same operations to agents, and live sync back to the source system is optional rather than assumed. The same shape applies to an Airtable exit: model the relations first, keep the source authoritative until reconciliation passes, then cut over.

• SQLite schemas model boards, items, and relations explicitly instead of treating the source tool as the schema.
• Custom MCP server (miro-custom-mcp) exposes the same operations to agents that the dashboard uses.
• Separate API, MCP, and web images so the sync worker scales independently of the UI.
• Optional live sync: the system is useful read-only before any write-back is enabled.

• GitHub Actions ci workflow plus a tests directory.
• Example payloads and notebooks are checked in for reproducing sync behaviour.
• RELEASING.md and CHANGELOG.md track versioned behaviour changes.

• Sync is scoped to the Miro object model, not a general no-code migration tool.
• SQLite is the reference store; a production migration would target Postgres.
• Not an Airtable connector. It is the pattern, applied to a different source system.

• README →github.com/Alexi5000/miro-workflows#readme
• MCP server →github.com/Alexi5000/miro-workflows/tree/master/miro-custom-mcp
• Schemas and server →github.com/Alexi5000/miro-workflows/tree/master/server