DesignCraft

Operate DesignCraft through its structured automation interfaces, preserving editable layouts and the user's chosen document.

References

Read references/control-protocol.md before constructing desktop requests. It is an unmodified upstream snapshot downloaded on 2026-10-08.

Source: DesignCraft control protocol. The documentation is distributed under the bundled MIT license. Relative links in the snapshot resolve against https://github.com/storytold/designcraft/blob/main/docs/.

For tool schemas, session modes, and coordinates, consult the upstream MCP documentation. For CLI script syntax, result references, and data merge, consult the agent guide. Discover installed command parameters when they differ from the snapshot; do not borrow flags or schemas from other ArtCraft applications.

Choose the session

Discover available DesignCraft tools, executables, and existing sessions first. Prefer a connected MCP server when available.

• To edit the user's running app, use desktop control or designcraft-cli mcp --connect PORT (also accepts HOST:PORT).
• For independent file processing, designcraft-cli mcp starts an in-process headless engine with an empty Letter document. Open the intended file before editing it. This mode does not change the user's live window.
• CLI scripts can process files or connect to the running app. Inspect designcraft-cli --help and the relevant subcommand before choosing arguments.