gridcraft

Installation
SKILL.md

GridCraft

Operate GridCraft through its structured automation interface. Preserve the user's requested workbook, formulas, and editable content.

Protocol reference

Read the relevant sections of references/control-protocol.md before constructing calls. This is the downloaded upstream protocol, captured on 2026-11-09.

Source: GridCraft control protocol. The documentation is distributed under the bundled MIT license. Relative links inside the snapshot (e.g. mcp.md, cli.md) resolve against https://github.com/storytold/gridcraft/blob/main/docs/. Discover installed command parameters through engine.commands rather than inventing them.

Select the session and authenticate

Start the desktop app with a control port: gridcraft --control 7979 (or GRIDCRAFT_CONTROL_PORT=7979). The port always requires a token; there is no way to turn this off. The app writes its token to $XDG_RUNTIME_DIR/gridcraft/control-<port>.token (else ~/.cache/gridcraft/…; Windows %USERPROFILE%\.gridcraft\…), or you can pin one with GRIDCRAFT_CONTROL_TOKEN (preferred over the visible --control-token). The first line of every connection must be {"id":0,"method":"auth","params":{"token":"…"}}; anything else closes the connection. gridcraft-cli send and gridcraft-cli mcp --connect handle auth themselves.

For headless work with no window, use gridcraft-cli mcp or gridcraft-cli run; that session is separate from the user's live app. Discover executables and running sessions first and reuse one when possible; this skill does not install GridCraft or configure MCP servers.

Transport

After auth, send newline-delimited JSON to 127.0.0.1:<port>; one request line, one reply line, matched by id, check ok. A line that is not a JSON object with a string method (over 64 MiB, non-UTF-8, an HTTP request) gets one error reply and closes the connection. Any method name that is a command id (e.g. home.bold) runs that command directly.

Installs
58
GitHub Stars
14
First Seen
Nov 2, 2026