Hi all!
I wanted to add four additional use-cases (via the videos below) which I believe are worth sharing with the community, as they open up new interesting possibilities:
Use case: Design to code.
Use case: Prototype interactions.
Use case: Scribble to design.
Use case: Design System documentation + Design tokens.
Why I think these are interesting:
-
They expand the “design ↔ code” workflow beyond simple export: we’re seeing automation, system governance and cross-team collaboration facilitated by the MCP Server.
-
In my experience working with design systems, one of the biggest friction points is keeping design changes, code, style guides and component libraries in sync. The MCP server may help reduce that friction.
-
They highlight avenues that the community (plugins, integrations, dev environments) could pursue. For example: automated checks on design-system compliance, automated versioning of design styles, developers and designers working off the same metadata.
Looking forward to seeing how the MCP Server evolves and how we can all build on it 
