Craft Apps do not share one universal automation command. Start with the app that fits your task, check its own MCP documentation and connect one supported tool at a time.
MCP lets an AI client call tools exposed by a server. Each app has its own server, arguments and permissions. Documentation support does not establish that a downloaded build includes its CLI or that a connection was tested.
The table is a documentation inventory checked on 20 October 2026. Repository versions identify the source snapshot, not necessarily your installed binary. Only CADCraft’s connection and drawing result are independently exercised in the linked sample; other entries are documentation findings. SolidCraft belongs to Tangency Labs and is covered separately, outside the thirteen official Craft Apps.
| Official app & source version | Documented tools and task | Evidence and connection status |
|---|---|---|
| PhotoCraft · source 0.10.0 | Layered image editing, command execution and document inspection; review the app-specific tool list before saving PSD copies. | App-specific MCP documentation ↗ · Documentation verified; this connection not independently tested. |
| VectorCraft · source 0.13.1 | Vector document commands and inspection; SVG/PDF exchange does not establish Illustrator editing-data fidelity. | App-specific MCP documentation ↗ · Documentation verified; this connection not independently tested. |
| FilmCraft · source 0.9.0 | Cut, trim, grade, mix and export via the shared engine command registry; native Premiere project import is excluded by the README. | App-specific MCP documentation ↗ · Documentation verified; this connection not independently tested. |
| LightCraft · source 0.9.1 | Photo-library and raw-development commands in headless or live-app mode; inspect the library and export settings. | App-specific MCP documentation ↗ · Documentation verified; this connection not independently tested. |
| PdfCraft · source 0.9.0 | PDF document automation; verify the tool list and each operation against the PDF task rather than assuming Acrobat feature parity. | App-specific MCP documentation ↗ · Documentation verified; this connection not independently tested. |
| EffectCraft · source 0.12.0 | Composition-tree and keyframe commands with rendered-frame inspection; no AEP/AEPX import or After Effects plug-in runtime. | App-specific MCP documentation ↗ · Documentation verified; this connection not independently tested. |
| DesignCraft · source 0.9.0 | Page-layout document automation; inspect layout and rendered output before exporting a copy. | App-specific MCP documentation ↗ · Documentation verified; this connection not independently tested. |
| FigCraft · source 0.7.0 | Interface-design command registry, design inspection and export; headless and attached modes have distinct arguments. | App-specific MCP documentation ↗ · Documentation verified; this connection not independently tested. |
| WordCraft · source 0.8.0 | Document command execution and inspect_document; documented automation read/write roots can confine file access. | App-specific MCP documentation ↗ · Documentation verified; this connection not independently tested. |
| SoundCraft · source 0.9.0 | Audio project automation with a documented demo server and read/write-root controls. | App-specific MCP documentation ↗ · Documentation verified; this connection not independently tested. |
| DeckCraft · source 0.8.0 | Slide-deck commands in headless or live-app mode; documented read/write-root controls apply to headless use. | App-specific MCP documentation ↗ · Documentation verified; this connection not independently tested. |
| CADCraft · source 0.9.0 | command_line and execute CAD commands, inspect entities and render/export drawing results; verify dimensions independently. | App-specific MCP documentation ↗ · Real v0.8.0 stdio MCP connection and drawing fixture; see CADCraft tutorial. |
| GridCraft · source 0.8.0 | read_range, write_range, set_cell and evaluate_formula are documented; inspect formulas and reopen an exported workbook. | App-specific MCP documentation ↗ · Documentation verified; this connection not independently tested. |
Use the official CADCraft CLI from the same release as your tested app. Our fixture starts cadcraft-cli mcp, performs the MCP initialize handshake and discovers its real tools before drawing. It uses the v0.8.0 server over stdio. A separate real Claude Code 2.1.304 health check reports both CADCraft and SolidCraft connected. No authenticated model generation was performed: tool execution and file verification used the standalone protocol fixture.
The verified drawing contains a 100 × 60 mm rectangle, radius-4 circle and a dimension measuring 100 mm. Save and reopen the DXF in CADCraft, inspect entities and dimensions, and check the exported image. The CADCraft MCP tutorial provides the actual task and downloadable results.
Install Claude Code using its official instructions and verify your app-specific CLI path and version. Open a new folder containing only a copy of your test project.
You can identify the CLI release and the exact folder the agent may edit.
If this fails: If the binary is missing, use the official app release or its build instructions; another app’s CLI is not a replacement.
Keep: Original sample and version notes.
Follow the matching release’s MCP document. CADCraft starts with cadcraft-cli mcp; use an absolute executable path when it is not on PATH. Review the generated client configuration before enabling it.
Your client reports the server connected and exposes its tool list. Documentation support alone is not a connectivity test.
If this fails: Read the process error and compare the release-specific arguments; headless mode and attaching to a running app differ.
Keep: Task-local MCP configuration, excluding credentials.
Ask for a millimetre drawing with a 100 × 60 rectangle and radius-4 circle, then inspect entities, dimension values and save a separate DXF.
The drawing, measurements, saved file and reopened file agree.
If this fails: Treat an agent’s success message as unverified until the file opens and the measurements agree.
Keep: Native drawing, DXF, genuine exported preview and task log.
MCP tools may create, overwrite or export local files. Restrict automation read/write roots where the particular server supports them, and work in a disposable test folder. Keep originals elsewhere. Do not pass secrets or private client documents to a demonstration task.
A server may run headless, attach through a local control port, or support both. A command copied from another Craft App can start the wrong mode or omit its permission flags. Recheck the app’s own documentation after updating.
Choose CADCraft for the checked drafting example. Use SolidCraft’s separate guide for a dimension-driven 3D part; its command names, ownership and file workflow are different.
Official sources checked 20 October 2026. Test results are limited to the versions, environment and files stated above.
Craft Apps Guide