# FigCraft (open-source Rust interface design tool with MCP)

> Updated 2026-10-26 · type: tool · category: productivity-knowledge · status: active · rev 1

FigCraft is a free, offline Rust design app that stands in for Figma-style tools, with an MCP server so AI agents can drive its 400+ commands.

- Open source: yes (MIT OR Apache-2.0)
- Self-hostable: yes
- Pricing: Free; no paid tier found.
- Best for: Founders, marketers and design-engineers who want a no-account, offline interface design tool that their AI agents can operate over MCP.
- Not for: Teams that depend on opening real Figma files reliably or need production stability: it is early alpha and .fig import is best effort, not checked against real documents.
- Version: 0.11.2
- Last verified: 2026-10-26

- **Canonical:** https://gtmstacker.com/registry/tool/figcraft/
- **Source:** [FigCraft: free Apache-2.0 Rust Figma alternative drivable by agents over MCP](https://x.com/RoundtableSpace/status/2113952392605823436) — RoundtableSpace
- **Tags:** productivity-knowledge, mcp-agents, design-tools, ui-design, rust, wasm, self-hostable, open-source
- **Repository:** https://github.com/storytold/figcraft
- **Version:** 0.11.2

## Is FigCraft (open-source Rust interface design tool with MCP) open source?

Yes, FigCraft (open-source Rust interface design tool with MCP) is open source under the MIT OR Apache-2.0 license.

## How much does FigCraft (open-source Rust interface design tool with MCP) cost?

Free; no paid tier found. (free).

## Can I self-host FigCraft (open-source Rust interface design tool with MCP)?

Yes, FigCraft (open-source Rust interface design tool with MCP) can be self-hosted (the source is available under the MIT OR Apache-2.0 license).


---

**FigCraft** (`storytold/figcraft`) is a free, clean-room **Rust** interface design app from **ArtCraft**, dual-licensed **MIT OR Apache-2.0**. It runs natively on macOS, Windows, Linux and FreeBSD, or in the browser as a WebAssembly build, offline, with no account and no telemetry. Its **MCP server** lets AI agents drive the same 400+ commands the UI uses.

## Provenance

- License **MIT OR Apache-2.0** (user's choice), from `Cargo.toml`, the root `LICENSE-MIT` + `LICENSE-APACHE` files and the README. GitHub's detector shows only Apache-2.0, so the "Apache-2.0" in the viral post's headline is incomplete.
- ArtCraft names, wordmark and logos are trademarks not covered by the license; forks must remove them.
- Repo under the `storytold` (ArtCraft) org, created 2021 with 68 public repos; not a fork, not archived. Lookalike check: other "figcraft" repos are unrelated or name collisions; this entry links only `storytold/figcraft`.
- Activity as of 2026-10-26 (GitHub API): **3,539 stars, 1,380 forks**; repo created 2026-10-09, last push 2026-10-26. Releases v0.8.0 (10-20) through **v0.11.2** (10-25); Cargo.toml still declares MIT OR Apache-2.0. README status: **early alpha**.
- MCP confirmed: `figcraft-cli mcp` (headless) and `figcraft-cli mcp --attach <port>` (drives a running app), JSON-RPC 2.0 over stdio, MCP protocol 2025-06-18, implemented in `crates/mcp`.
- Self-hosting: native app plus WASM web build; an optional self-hosted `figcraft-server` collaboration server (Linux, Docker/systemd) is in preview.
- Pricing: free; no paid tier found.
- **Vendor claims:** "about 49% of the way to replacing proprietary tools" and sub-millisecond node creation in 20,000-node files are the README's own estimates.
- The original X post could not be fetched (HTTP 402); everything here is from the primary source. Curated and verified in run `2026-10-24-registry-update-01` (step-3 verification, 2026-10-24).

## Why it matters for a GTM stack

Landing pages, ad creative and product mockups usually mean paid design seats, and agents can only help inside closed tools on the vendor's terms. FigCraft is a permissively licensed design app that runs offline and exposes its whole command set over MCP, so an agent can lay out frames and components directly. It is two weeks old and openly calls itself early alpha, and Figma file import is best effort, so treat it as a fast-moving experiment rather than a drop-in replacement for an existing design workflow.