Every command in all 18 Artcraft apps — 8,873 commands with exact IDs, ready for Claude and ChatGPT.
18 appsPhoto, vector, video, PDF, layout, audio, CAD, spreadsheets and more — one registry behind all of them.
8,873 commandsEvery ID verified against its app’s current release. Nothing invented, nothing guessed.
Current as of 9 November 2026All 18 lists match their current release. Re-checked weekly; the stamp at the bottom of this page says when it was last verified.
Use it as a parts list, not a read-through. Find the exact command for the job, hand that ID to your assistant, test it once, then save the working version so you never have to hunt for it again.
Start here
One registry behind everything
In every Artcraft app, the toolbar, the menus, the command palette, scripts, the CLI, the JSON control channel and the MCP server all call the same thing: Session::execute(id, params). A command’s ID — like layer.duplicate — is identical on every surface. Learn the ID once and you can use it in the app, in a script, from a terminal, or by asking Claude or ChatGPT to run it.
PhotoCraft’s current release (v0.22.0) lists 1,005 commands. Every app below carries its own count and the release its list was taken from.
For the overview companion — what each app is for and which to install first — see theCrafting Apps field guide.
Current as of 9 November 2026
All 18 lists on this page match their app’s current release: 8,873 commands in total.
SolidCraft: 570 listed — 443 enabled, 127 listed but not enabled.
AniCraft: 113 commands from source. No release yet — subject to change.
Using this guide
From lookup to a working job
Use this guide as a parts list, not a read-through. Find the exact command for the job, hand that ID to your assistant, test it once, then save the working version so you never have to hunt for it again.
Start with the outcome, not the app. Search the Command explorer for what you want to happen — watermark, duplicate, export, resize — then filter by app. If nothing matches, open that app’s chapter and scan its top categories: the category names show where the app is strong (PhotoCraft is layer and filter-heavy; PdfCraft is form, page and comment-heavy).
Pin the exact ID. Use the Copy ID button on the explorer row and keep the ID verbatim — punctuation and capitalisation included. layer.duplicate in the prompt beats “duplicate the layer, please” because every surface — app, CLI, script and MCP — accepts the same ID.
Pick the surface for the job. One-off work in a file you have open: MCP or bridge mode. The same job over and over: CLI run, batch, or the serve JSON-lines server. Unsure? Start with MCP — it can list the live registry itself with command_list.
Test on a copy first. Run the job on a duplicate file, check the result (over MCP, ask for a render_preview; ui_screenshot only works in live bridge mode), and only then run it on the real file or the whole folder.
Save the job, not just the output. Record the five things in the job sheet below. That record is what turns a good one-off into a skill or automation you can reuse next month.
Job sheet field
What to record
App + release
e.g. PhotoCraft v0.22.0
Command IDs
In the order they run
Parameters
The JSON you actually used
Folders
Read root in · Write root out
Check
How you know it worked
Point your AI at this guide
Three levels, depending on how your assistant is set up. All three use the same rule: the assistant works from IDs in this guide or from the app’s own command_list — it does not guess IDs.
Assistant can open this page
“Use the Artcraft Apps User Guide on this page as your reference. Find the PhotoCraft commands for [job]. Tell me the exact IDs you plan to use and their parameters before you run anything. If an ID is not in the guide, say so — do not invent one.”
Assistant is connected over MCP
“Call command_list first and show me what you found for [job]. Open the file with doc_open, run the commands, save with doc_save / export with doc_export, and show me a screenshot of the result. Ask before anything destructive.”
Remember: file-path commands are refused over MCP — that is expected, not an error to work around.
Building a skill or automation
“Build a reusable skill from this. Inputs: a folder of source files. Steps: the command IDs listed, in order, with these parameters. Outputs: finished files in the write folder, named [pattern]. Stop and report if a command fails or an ID is missing. Include a test run on one file first.”
Paste in the relevant chapter or explorer rows — not the whole guide — plus your job sheet.
For a pipeline with no assistant in the loop, the same IDs go straight into the CLI:<app>-cli run --cmd <id> --params '<json>' for one job,batch / command_batch for a folder, and serve when another program needs to keep sending jobs. Keep the read and write roots separate so a bad run can never overwrite your originals.
For your business
Maker use cases
Six jobs most maker shops repeat every week, matched to the apps and command families that actually do them. Each one follows the same pattern above: find the IDs, test on a copy, save the job sheet.
PhotoCraft · LightCraft
Product photos, batch-ready for listings
Sort and develop a shoot in LightCraft (library, develop, preset), then finish in PhotoCraft (layer, filter, file): consistent crop and size, background cleanup, and a watermarked and clean version of every shot — the same steps, every product.
Ask your AI: “Develop these photos with the shop preset, export listing-size copies, and add the watermark layer to the copies only. Keep the originals untouched.”
VectorCraft · DesignCraft
Design files to cut-ready and print-ready
Clean up artwork in VectorCraft (object, path, text — including its addon.* arrange tools for laying pieces out in a grid), then build the customer-facing sheet in DesignCraft (layout, table, style): size chart, material notes and care instructions on one page.
Ask your AI: “Arrange these designs in a grid with even spacing, convert the text as specified, and lay out the instruction sheet from the template.”
PdfCraft · 200 MCP tools
Downloads customers actually receive
Patterns, instructions and order forms as finished PDFs: doc_header_footer and doc_watermark for branding, form_* tools for fillable order and personalisation forms, accessibility_check before you publish, and doc_batch / action_run when the same fix applies to a whole folder of files.
Ask your AI: “Add the shop header and watermark to every PDF in this folder, run the accessibility check, and report any file that fails.”
GridCraft · WordCraft · DeckCraft
Pricing, paperwork and pitches
GridCraft (data, formulas, pivot) for price lists, material costs and inventory counts. WordCraft (table, insert, mailings) for quotes and wholesale terms you send repeatedly. DeckCraft (slide, design, format) for the craft-fair, wholesale or sponsor deck you keep updating.
Ask your AI: “Update the price sheet from this cost list, flag anything where the margin drops, and rebuild the deck with the new prices.”
FilmCraft · EffectCraft · SoundCraft
Listing video and social clips
FilmCraft (timeline, captions, transcript, export) to cut a making-of clip, caption it, and export it sized for the listing and for social. EffectCraft (templates, renderQueue) for the intro or title treatment you reuse. SoundCraft (edit, track, mix) to clean up the voiceover.
Ask your AI: “Cut this to 60 seconds, add captions from the transcript, apply the shop title template, and export both versions.”
CADCraft · SolidCraft
Jigs, fixtures and packaging
CADCraft for 2D drawings and templates; SolidCraft (sketch, solid, component) for the 3D jig, stand or packaging insert you will print or cut more than once. In SolidCraft, check the explorer flag before you rely on a command — 127 of its listed commands are not enabled yet.
Ask your AI: “List the enabled sketch and solid commands first, then model the jig from these measurements and export it for printing.”
None of these need new software. Each one is the apps above, driven through the CLI or MCP surfaces in How Claude & ChatGPT actually run commands, with the command IDs taken from the explorer and chapters that follow.
The mechanism
How Claude & ChatGPT actually run commands
There are four surfaces, and they all reach the same registry. Verified from the PhotoCraft repo docs (book/src/automation/cli.md, book/src/automation/mcp.md, docs/mcp.md) and the other apps’ CLIs.
The CLI registry. Every app ships a command-line tool next to the desktop app. <app>-cli commands prints the full registry — as JSON with--json where supported; as plain JSON for CADCraft, DesignCraft and MaterialCraft; and as a plain-text table for DeckCraft, SoundCraft and TextureCraft.
photocraft-cli commands --json
Run commands headlessly.run executes any command by ID with JSON parameters — no GUI needed. The CLI’s other subcommands are convert,info, batch, droplet, and serve — a JSON-lines headless server over stdio or TCP, handy for pipelines.
photocraft-cli run --cmd layer.duplicate \
--params '{"name":"Copy"}'
MCP — the AI-native surface.<app>-cli mcp starts an MCP server over stdio (protocol version 2025-06-18) that any MCP-capable assistant can attach to. Register it once, then just ask in plain language:
PhotoCraft exposes 25 generic MCP tools — including command_run, command_batch, command_list, doc_open, doc_save, doc_export and ui_screenshot — which together reach its whole registry. PdfCraft takes the opposite approach: 200 specific tools, one per operation, with a --compact on-demand mode (full list under PdfCraft MCP tools).
Bridge mode — drive the open app. The MCP server can bridge to a desktop app you already have running, started with <app> --control <port>, using a private token file. Bridged tools add live UI inspection and control on top of the registry:
AniCraft’s MCP surface follows the same pattern with five tools — anicraft_commands (list/filter), anicraft_run, anicraft_run_script, anicraft_document and anicraft_render — and requires confirm: true before destructive commands.
Where the CLI lives
On Linux, deb/rpm installs put it at /usr/bin/<app>-cli. On macOS it ships as a separate <app>-cli-<version>-macos-<arch>.zip. On Windows it’s at %LOCALAPPDATA%\Programs\ArtCraft\<App>\<app>-cli.exe. You can also build it from source withcargo install --path apps/<app>-cli --locked.
One rule to know
File-path commands are refused over MCP. When an assistant works through MCP it should open, save and export via doc_open / doc_save / doc_export — or drop to the CLI for direct file paths. If a request mysteriously fails over MCP, this is the first thing to check.
Beyond the desktop
15 of the 16 official apps also compile to WebAssembly and can run in a browser — every official app except FilmCraft. There is no iPad app: Artcraft is desktop (macOS, Windows, Linux — Windows ARM64 builds exist) plus those browser builds.
Command explorer
Every command, searchable
8,873 commands across 18 apps. Search by what you want to happen, filter by app, and copy the exact ID. Chapter lists load on demand so this page stays fast — searching loads every chapter.
Stay current
Get the install guide, and word when this guide updates
Leave your email and we’ll send the Artcraft install guide — get Artcraft installed and connected to your AI agent, then run a first command. You’ll also hear when a new release changes the command lists on this page. No spam, no sharing your address.
For Hub members
The template pack: start from a working setup
The guide tells you what exists. The pack gives you a working starting point: a Claude skill for listing photos with PhotoCraft, the Claude Desktop settings that connect PhotoCraft, and a fill-in job sheet. We ran the skill end to end on PhotoCraft 0.22.0 before putting it here.
Listing-photos skill: a ready-to-upload Claude skill that crops, sizes, adjusts and sharpens a product photo, adds your logo as a faint watermark, and saves a listing JPG plus a layered master.
Claude Desktop settings: a Mac file and a Windows file that connect PhotoCraft to Claude, with your CraftWork folder as the only folder it can touch.
Job sheet: the five fields from this guide, as a fill-in file you reuse for every job that works.
Once you're signed in, the files come with a link to the step-by-step setup. Keep that link: the steps live there in case you lose this page.
This pack is for Maker Growth Hub members. If you’re not a member yet, the button at the bottom of this page joins the Hub — members get the pack, the live walkthrough, and the rest of the member toolkit.
Keep it current
Refresh any list in one command
Because every app can enumerate itself, this guide never has to stay stale. To rebuild any app’s chapter from the current release:
Install or update the app (the ArtCraft Launcher handles the 16 official apps plus SolidCraft).
Run the app’s own registry dump: <app>-cli commands --json (plain JSON for CADCraft/DesignCraft/MaterialCraft; a text table for DeckCraft/SoundCraft/TextureCraft).
Diff the IDs against the explorer above — new, renamed and removed commands are the delta between the catalog version labelled on each chapter and today.
For PdfCraft, also compare its MCP tool list, and for PhotoCraft remember the generic-tool surface (command_list over MCP returns the live registry without any file at all).
Counts on this page were verified on 2026-11-09 against the current releases. Every chapter carries the release version its list was extracted from, next to its count.
Current as of 9 November 2026 · Lists re-checked weekly
Questions
Before you install anything
Is Artcraft free?
Yes. Artcraft is a free, open-source creative suite. You install it with the ArtCraft Launcher, which handles the 16 official apps plus SolidCraft as a community app. There is no paid tier and no account needed to use the apps.
Does Artcraft run on an iPad?
No. Artcraft is desktop only — macOS, Windows and Linux — plus WebAssembly builds that run in a browser. There is no iPad app, and the Launcher does not offer an iPad install.
What is a command ID, and why does this guide list IDs instead of menu paths?
In every Artcraft app the toolbar, menus, command palette, scripts, CLI, JSON control channel and MCP server all call the same thing: Session::execute(id, params). A command’s ID — like layer.duplicate — is identical on every surface. Learn the ID once and you can use it in the app, in a script, from a terminal, or by asking Claude or ChatGPT to run it.
Should I use MCP or the CLI?
One-off work in a file you already have open: MCP or bridge mode. The same job over and over: the CLI run, batch, or the serve JSON-lines server. Unsure? Start with MCP — it can list the live registry itself with command_list.
How current are the lists on this page?
All 18 lists match their app’s current release as of 9 November 2026 — 8,873 commands in total. Every chapter carries the release version its list was taken from, next to its count, and the lists are re-checked weekly.
Why are some SolidCraft commands marked “not yet implemented”?
SolidCraft lists 570 commands, but 127 of them are listed by its CLI and not yet enabled. They are marked in the explorer so you never build a job around a command that cannot run yet. The 443 enabled commands work.
What about AniCraft — can I install it?
Not yet. AniCraft is in development and has no release. Its 113 commands in this guide were taken from the source registry, so they are subject to change before the first release.
The guide is free. The system around it isn’t.
Turn the commands into a shop that runs
The Maker Growth Hub is where the workflows, the live walkthroughs and the 1:1 help live — including the walkthrough for this guide and the template pack above.