AI NewsOpen sourceAnnouncement
FigCraft is an open-source Figma alternative that AI agents can drive
ArtCraft released FigCraft, a Rust interface-design app whose 400 or so commands are reachable through a CLI and an MCP server, so a coding agent can edit a design file the way a designer would.
Image: GitHub
Why it mattersA design tool whose every menu item is also a scripted command lets a product team move a mock from Figma into source control, open it from an agent and run routine edits without a seat per designer.
A free interface-design app that keeps frames, components with variants, auto layout, vector networks and prototyping, and lets a coding agent call every one of its commands through an MCP server, is now the alternative that teams on a Figma subscription did not have ten days ago. FigCraft, the next entry in the ArtCraft open-source series, is a Rust desktop app the project describes as a from-scratch rebuild of collaborative interface design, written without reading the original source. The GitHub repository was created on 9 October 2026 and had 2,605 stars by 18 October, with 989 forks and 166 open issues.
The source is dual-licensed under MIT or Apache-2.0, and the ArtCraft organisation has released ten other open-source alternatives this month, including PhotoCraft, VectorCraft, SoundCraft and CadCraft. FigCraft runs on macOS, Windows and Linux as a native app, and the project tag calls it "early alpha" at version 0.5.1.
The Figma workflow, feature by feature
The README lists layouts with auto layout, wrap, grid and constraints, components with variants, instances and overrides and an Assets panel, vector networks edited with Pen and Pencil tools with booleans and variable-width strokes, paints and effects covering gradients, image fills, shadows, blur, noise and glass, typography with OpenType features, variable fonts and right-to-left text, and prototyping with connections, triggers, Smart Animate transitions and variables. A Dev Mode generates React, CSS and HTML from a selection. Export writes PNG, JPG, WebP, SVG and PDF. Live sessions carry cursors, selections and a cursor chat for multiplayer editing.
What the project says about coverage
The README states FigCraft is "in alpha: about 49% of the way to replacing proprietary tools for real work". The repository notes that edits touch only what changed, so creating a node in a 20,000-node file takes a fraction of a millisecond. Import of .fig files is called best-effort. Treat the coverage figure and the import support as the project's own: nobody independent has measured them.
The CLI and the MCP server
Every tool, menu item and prompt in FigCraft is also a command with an id, reachable from the keyboard, a figcraft CLI, a JSON control channel and an MCP server. The project pitch on getartcraft.com calls this "agent-ready" and lists more than 400 commands. A script can open a file, change a component variant across every instance, re-export the icon set at three sizes and commit the result. A designer who touches a file every day can keep working in it with the plugin surface and WebAssembly plugin runtime the README names. A product team that uses Figma mostly as a read surface, where developers open a file once a week to copy a hex value or hand off a spec, can read and edit those files from a pull request today without buying a seat each. A team whose daily work depends on Figma's library sync, FigJam, or large legacy .fig imports has to wait on the alpha milestones the project lists.
Source
storytold/figcraft on GitHub and the FigCraft page on getartcraft.com.
This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.
Get AI News in your inbox
New developer tools, model and agent releases, and how teams are actually using them to release software. Short, and only when there is something worth reading.
