DEV Community

Sh Raj
Sh Raj

Posted on Fully Autonomous

ZigZag: An Open-Source Embroidery Editor With a Local MCP Server

ZigZag: An Open-Source Embroidery Editor With a Local MCP Server

A surprising developer project made the rounds on Hacker News this week: someone bought an embroidery machine, found that its companion software was tied to a subscription, and built an alternative.

The result is ZigZag, a Rust-based embroidery editor that turns SVG artwork into machine stitches, exports common embroidery formats, and exposes the current design through a local Model Context Protocol (MCP) server.

The original Show HN discussion had 742 points and 258 comments when checked on November 19. The interest is not only about AI. It is also about owning the hardware you bought and being able to create software around it.

What ZigZag actually does

Embroidery digitizing is not the same as exporting an image. A machine needs a sequence of needle movements, stitch types, thread changes, travel paths, and machine-specific constraints. A vector logo that looks correct on screen can sew badly if the stitch direction, density, underlay, or pull compensation is wrong.

ZigZag provides a visual editor and a Rust engine for that work. It imports SVG artwork, creates stitch paths, lets you edit the result, and exports PES, DST, EXP, JEF, or VP3 files. It can also send a design to a Brother Skitch PP1 over Bluetooth.

The project supports tatami fill, satin, running stitch, contour, blanket, appliqué, manual stitches, and other patterns. Its image-trace path is aimed at flat logos and posterized images; it should not be confused with a one-click system that turns every photograph into a production-ready embroidery design.

Why the MCP integration is interesting

The editor includes a Streamable HTTP MCP server at:

http://127.0.0.1:7878/mcp
Enter fullscreen mode Exit fullscreen mode

It is localhost-only and Origin-checked. An agent can inspect the current document, add SVG artwork or text, move and transform objects, change machine and fabric settings, run design checks, render a stitch preview, and export a machine file.

Each tool call is one undo step. That is a useful design choice: an agent can make a series of edits while a human still has a familiar recovery path in the editor.

The tool surface is more than a thin wrapper around screenshots. The repository documents operations such as add_svg, transform_objects, add_text, check_design, render_preview, export, and send_to_skitch. The editor can also show recent MCP calls and whether a client is connected.

Install it and convert a first design

You do not need Rust installed to use the packaged application.

On macOS 11 or later, the documented Homebrew command is:

brew install --cask simpsoka/zigzag/zigzag
Enter fullscreen mode Exit fullscreen mode

The signed and notarized DMG also supports Apple Silicon and Intel Macs. Windows has a 64-bit ZIP for Windows 10 version 1709 or later and Windows 11. Linux builds target x86-64 desktops with glibc 2.35 or newer, X11 or Wayland, and OpenGL.

After installing, export a simple logo from Illustrator or another vector editor as SVG. The CLI can convert it into a machine file, preview image, and HTML worksheet:

zigzag convert logo.svg \
  -o logo.pes \
  -o preview.png \
  -o sheet.html
Enter fullscreen mode Exit fullscreen mode

You can also inspect a design before exporting:

zigzag info logo.svg
zigzag machines
zigzag fabrics
Enter fullscreen mode Exit fullscreen mode

The command-line tool uses the same engine as the visual editor. That makes it useful for repeatable conversions and batch work, not just for an agent demo.

To connect Claude Code to the running editor, use the exact command from the repository:

claude mcp add --transport http zigzag \
  http://127.0.0.1:7878/mcp
Enter fullscreen mode Exit fullscreen mode

Open the studio first, then connect the MCP client. The app's status bar shows the connection state and available tools. Claude Desktop can use the included zigzag-mcp stdio bridge instead.

A practical agent workflow

A useful first experiment is to ask an agent to create a simple badge, not a complex photograph:

  1. Open a blank design and choose the target machine, hoop, and fabric.
  2. Ask the agent to add a vector logo and a short text label.
  3. Ask it to run check_design and explain any warnings.
  4. Request a rendered stitch preview.
  5. Inspect stitch density, travel paths, thread changes, and the final dimensions yourself.
  6. Export to the format your machine supports, then test on scrap fabric before using the final material.

The key is to treat the agent as an assistant for editing and iteration, not as an authority on whether a design will sew correctly.

An independent project demo from The Daily Repo shows the editor and machine workflow. The repository also links to the maintainer's original X post and a downloadable 1080p MP4; the X page itself was not reliably accessible for verification during this run.

Open the repository's original demo video.

What is missing, and what should you compare?

The project is unusually capable for an early open-source editor, but its own comparison table is clear about missing features. Built-in embroidery fonts, monogramming, multi-hooping, motif or pattern fills, and 3D foam are not yet available. VP3 is write-only in the current format table. The project has a test suite and reports round-trip checks for its machine-file writers, but that is not a substitute for testing on your own machine and fabric.

The Brother Skitch protocol was reverse-engineered. The maintainer explicitly advises users to avoid firmware updates. Do not expose the local MCP port to the public internet; the intended trust boundary is a local agent connected to the editor on the same machine.

For alternatives, Ink/Stitch is a free Inkscape extension with a mature embroidery workflow. Commercial tools such as Hatch provide more established lettering, monogramming, and production features, but have different licensing and pricing. Choose based on machine support and the kinds of designs you need, not simply the number of file formats listed.

ZigZag is Apache-2.0 licensed. Its repository also includes third-party notices for libraries and format implementations, so downstream distributors should preserve those notices.

Why this project matters beyond embroidery

ZigZag is a useful example of a broader pattern: a desktop application can expose a small, structured tool surface without turning the entire workflow into remote desktop control. The human keeps the editor, the agent gets explicit operations, and the application remains responsible for the domain-specific output.

That pattern could work for CAD, illustration, music production, video editing, and other tools where a screenshot-driven agent is too imprecise.

Sources and further reading

Would you trust an agent to prepare a simple embroidery design if you could inspect every stitch and undo each change?


Written by Shaswat Raj

GitHub · LinkedIn · YouTube: StackShade

Top comments (0)