DeckCraft

Operate DeckCraft through its structured automation interfaces, preserving editable slides and the user's chosen presentation.

References

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

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

For MCP tools and session modes, consult the upstream MCP documentation. The repository documents installation and supported workflows. Discover installed command parameters when they differ from the snapshot; do not borrow flags or schemas from other ArtCraft applications.

Locate the executables and choose the session

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

• For the user's open presentation, use desktop control or deckcraft-cli mcp --connect PORT. This operates the same deck as the visible app.
• For independent file processing, deckcraft-cli mcp starts its own headless engine. Open the intended presentation before editing it; this session does not change the user's live window.
• For one-off file operations, use deckcraft-cli info, run, render, or convert. Each invocation has its own session. Use run --in FILE to continue work on a saved deck; --sample loads the built-in sample, not the user's presentation.