Home / ArtCraft MCP
Our reading: yes, but not in the AI studio. All 13 Craft command-line tools have an MCP server, which we checked in each repository on Oct 19, 2026, so an agent such as Claude can edit images, documents and PDFs with no window open. We ran three of them that day, and each wrote a real file. The ArtCraft studio's own MCP server is still an open pull request.
MCP here means a small server an AI agent talks to with text messages, so it can call tools. This page separates what we ran on Oct 19, 2026 from what the official docs say. We sent the protocol messages ourselves. We did not run them inside Claude, Cursor, or any other client.
People searching this name can land on either of two projects. Only one of them is something you can run today.
| Which one | What it is | Status that day |
|---|---|---|
| Craft app command-line tools | Each app's *-cli program can start an MCP server. Twelve repositories have a docs/mcp.md. FilmCraft has no such file; its command-line source has an mcp subcommand. | Published. We ran three of them. |
| ArtCraft studio | The AI studio in storytold/artcraft. Pull request #1982 is titled "feat(mcp): Add full 61-tool ArtCraft Model Context Protocol server, CLI suite & agent skills". Issue #2003 is a proposal for library, generation and 3D Stage access. | Both still open. #1982 is not a draft and is not merged. Its last update was Oct 7, 2026. #2003 was last updated Oct 10, 2026. We did not run it. |
On Oct 19, 2026 we asked GitHub, for each of the 13 apps, whether docs/mcp.md exists. FilmCraft returned not found, so we read its command-line source. "Yes" below means one of those two checks passed. We did not run the other ten.
| App | MCP server | What we found |
|---|---|---|
| PhotoCraft | yes | docs/mcp.md |
| VectorCraft | yes | docs/mcp.md |
| FilmCraft | yes | No docs/mcp.md. The command-line program has an mcp subcommand. |
| LightCraft | yes | docs/mcp.md |
| PdfCraft | yes | docs/mcp.md |
| EffectCraft | yes | docs/mcp.md |
| DesignCraft | yes | docs/mcp.md |
| FigCraft | yes | docs/mcp.md |
| WordCraft | yes | docs/mcp.md |
| SoundCraft | yes | docs/mcp.md |
| DeckCraft | yes | docs/mcp.md |
| CADCraft | yes | docs/mcp.md |
| GridCraft | yes | docs/mcp.md |
PhotoCraft 0.10.0 was published Oct 18, 2026. WordCraft 0.8.0 and PdfCraft 0.9.0 were published Oct 17, 2026. We used the macOS universal command-line package for each, started as photocraft-cli, wordcraft-cli or pdfcraft-cli with mcp. No desktop window was open. All three accepted protocol 2025-06-18. Every timed step finished in under a second. The three zip files matched the GitHub digest, and macOS accepted them as notarized Developer ID software from Learning Machines LLC.
| App | Version | Tools | What we had it do | File |
|---|---|---|---|---|
| WordCraft | 0.8.0 | 16 | A blank document, the title ArtCraft MCP in bold, then the line "This line was written by the WordCraft MCP server." Nine calls, none an error. | mcp-test.docx |
| PhotoCraft | 0.10.0 | 25 | An 800×600 canvas, background #123A5F, and a rectangle filled #F2C14E. Four calls, none an error. Saving warned that 2 layers were flattened. | mcp-test.png |
| PdfCraft | 0.9.0 | 170 | Opened the WordCraft pdf, inserted a blank page 2, and wrote PdfCraft MCP on that page. The edit calls were not errors. The saved file has 2 pages. | mcp-test.pdf |
This is one real request we sent to PhotoCraft, and the reply. The fields and values are unchanged.
{"jsonrpc":"2.0","id":100,"method":"tools/call","params":{"name":"doc_new","arguments":{"width":800,"height":600,"background":"#123A5F","name":"mcp-test"}}}
{"jsonrpc":"2.0","id":100,"result":{"content":[{"type":"text","text":"{\"document\":0}"}],"isError":false}}
WordCraft also saved a one-page pdf under a different name, so PdfCraft could use mcp-test.pdf. Tool names are not the same across apps: WordCraft uses new_document and save_document; PhotoCraft uses doc_new, doc_save and command_run; PdfCraft uses doc_create, doc_save and command_run.
From the official docs — we tested with raw MCP messages, not inside these clients. The WordCraft doc shows this Claude Code command:
claude mcp add wordcraft -- wordcraft-cli mcp
The PdfCraft doc shows this client config. The path in it is the doc's placeholder, not a folder on our machine:
{"mcpServers": {"pdfcraft": {"command": "/abs/path/target/release/pdfcraft-cli",
"args": ["mcp", "--automation-read-root", "/work/project", "--automation-write-root", "/work/project/out"]}}}
What we actually started, with our own folder names removed, was the macOS universal command-line package:
photocraft-cli mcp --automation-read-root <read-folder> --automation-write-root <write-folder>
wordcraft-cli and pdfcraft-cli take the same two flags. PdfCraft's doc also describes --root. We did not pass it.
The read root and the write root are separate. A file the server writes is not automatically a file it may read back. We had to copy WordCraft's pdf into the read folder before PdfCraft would open it. That copy was ours, not the server's.
We asked PdfCraft to open /etc/hosts. The reply was an error (isError: true). Shortened only in the middle, where our read-folder path stood:
automation path rejected: outside the read root …: /etc/hosts
PhotoCraft was not given a path outside its roots, so we do not claim it blocks one. Its doc says that without a root that kind of file access is absent, and that paths have to sit under the root you pass. That sentence is the doc, not a test we ran.
mcp subcommand. We did not start them.--connect to a desktop app that is already open.docs/mcp.md, and FilmCraft's command-line program has an mcp subcommand. We ran PhotoCraft, WordCraft and PdfCraft on Oct 19, 2026. The ArtCraft studio does not have a shipped MCP server. Pull request #1982 is still open.mcpServers JSON block. We have not run those clients. Our test sent raw MCP messages to the three command-line tools./etc/hosts was rejected as outside the read root, with isError: true. PhotoCraft was not given an outside path. Give the server a read folder and a write folder on purpose.