ArtCraft MCP: Use the Crafting Apps from Claude, Codex and Cursor

The official answer is not a repository — it is a flag. Each Crafting App’s CLI has an mcp subcommand (for example gridcraft-cli mcp or wordcraft-cli mcp) that starts a Model Context Protocol server exposing the app’s full command set to AI agents. The storytold organization publishes each app’s protocol documentation in its repository under docs/mcp.md; there is no standalone “ArtCraft MCP” download.

The protocol is the standard MCP surface: newline-delimited JSON-RPC 2.0 over stdio, speaking protocol version 2025-06-18 while also answering older 2025-03-26 and 2024-11-05 clients. Logs go to stderr so the JSON stream stays clean. That means any MCP client that can spawn a process — Claude Desktop, Claude Code, Codex, Cursor, Windsurf — can drive the apps through the ArtCraft MCP without custom glue.

Two backend modes exist. Headless mode starts the app without a visible window and works on a file directly. Remote mode attaches to a running app: start the application with --control 7979, then connect the CLI with --connect 7979 — and the agent can not only run commands but also click, type and take screenshots, because it is driving the real interface.

The table below lists the verified MCP entry points. The pattern is uniform: each app’s ArtCraft CLI plus mcp — so people talk about the GridCraft MCP or the WordCraft MCP, but it is the same mcp subcommand every time. Tool sets differ per app because each exposes its own command vocabulary — WordCraft counts 422 commands and FilmCraft 650+, and GridCraft exposes workbook-oriented tools.

In GridCraft the MCP tools include execute_command, list_commands, inspect_workbook, read_range, write_range, set_cell and get_cell, evaluate_formula, insert_chart, create_table, sort_range, filter, open_workbook and save_workbook, undo and redo, screenshot and list_functions — a spreadsheet agent’s whole vocabulary. The same shape repeats in the other apps with their domain tools.

Because every app documents its own current tool list in docs/mcp.md, treat this page as the map and the per-app docs as the territory: the suite releases weekly, and tool lists grow with each release.

The most useful line in the official docs is in WordCraft’s docs/mcp.md, and it applies to every app: the --automation-read-root and --automation-write-root sandbox flags are consistent across the suite, so one client configuration works across the apps. Those flags sandbox what an agent may read and write on your disk — set the write root to a project folder and the agent cannot touch anything outside it.

A minimal Claude Code setup shows the pattern. Add one server per app you want to drive: claude mcp add gridcraft -- gridcraft-cli mcp, and repeat with wordcraft-cli, deckcraft-cli and so on. In Claude Desktop or Cursor, the equivalent config spawns the same command with the same sandbox flags in args.

Because the flags are suite-wide, you can write one config block and copy it per app, changing only the binary name. That is the piece no other ArtCraft MCP page can offer: the team standardized the agent surface before the apps even shipped.

Claude Code is the shortest path to the ArtCraft MCP: claude mcp add gridcraft -- gridcraft-cli mcp adds the server, and the agent can immediately inspect a workbook, evaluate a formula or render a screenshot. Repeat per app, and use the sandbox flags in the command if the agent will touch real files.

Claude Desktop and Cursor read a JSON config instead. The ArtCraft MCP server entry is a stdio command: command points at the app’s CLI binary, args contains mcp plus the automation roots, and the client spawns it on demand. After editing the config, restart the client and the app’s tools appear in the tool list.

Two practical tips from the official docs. First, remote mode is better for watching what the agent does: start the app yourself with --control 7979 and connect the CLI with --connect 7979, then every click and keystroke happens in a window you can see. Second, keep the write root narrow — the agent has the same command surface as the UI, and undo exists but trust is cheaper.

Search results for artcraft mcp also surface three community repositories: theCosmicCrafter/artcraft-mcp (18 stars, Rust, packaging the media API servers and schemas), smoermeow/artcraft-mcp (4 stars, Python, written for the Hermes agent) and matrixNeo76/artcraft-mcp-bridge (0 stars, Python, new as of Oct 13). They are useful projects, but they do something different.

Those repos connect to the ArtCraft generative-media subscription API — the paid service for image, video and 3D generation at the heart of the ArtCraft AI product. They do not drive the Crafting Apps: an MCP client wired to them can request a generated image, not edit a spreadsheet. If your goal was to let Claude drive GridCraft or WordCraft, the built-in CLI servers in the sections above are what you want.

A quick disambiguation rule: official agent capability lives inside each app’s repository as docs/mcp.md and the <app>-cli binary; anything that is a separate repo named artcraft-mcp is community media-API work. Both are legitimate — they are just different products.

PSDraw hosts the unmodified official web builds of the Crafting Apps and documents them; it does not operate the MCP servers, which run on your machine against your local files. The cleanest setup is: install the desktop app or CLI for the app you want to automate, add its ArtCraft MCP server to your client, and keep browsing here for the guides. Nothing on this page requires an account or a subscription.

PSDraw does not ship its own MCP server. Our tools are browser-based and run entirely on your device, so there is no local process for an agent to attach to — and the searches that bring people to this page are about the Craft apps, not about PSDraw.

If you want the full command surface per app, skip to the app’s own docs: each repository’s docs/mcp.md is versioned with the app, and the ArtCraft GitHub guide lists every repository in one table.