t1k:figcraft
| Field | Value |
|---|---|
| Module | t1k-ual |
| Version | 2.9.56 |
| Effort | low |
| Tools | Bash, Read |
Keywords: figcraft, figcraft mcp, figcraft.the1studio.org, publish figcraft, selfhost figcraft, share figcraft file
How to invoke
Section titled “How to invoke”/t1k:figcraft[publish | mcp | plugin | troubleshoot]FigCraft: Company Server and MCP
Section titled “FigCraft: Company Server and MCP”FigCraft is the studio design-file app. The company runs a self-hosted FigCraft server. This skill covers sharing a .figcraft file to it, driving a running app over MCP, and the one failure mode that is server-side.
Decision Tree
Section titled “Decision Tree”| Intent | Path |
|---|---|
Share or publish a .figcraft file to the company server | Publish a file |
| Let an agent drive a running FigCraft app | Drive the app over MCP |
| Publish a plugin folder | Publish a plugin |
| Server returns 502 or will not connect | Troubleshoot |
Server address
Section titled “Server address”wss://figcraft.the1studio.org/?key=5vaBsg_kWnk7GOMuDSK4OgThe server is reachable only on the studio NetBird VPN. Check the VPN first (t1k:vpn, netbird status).
Key placement: this kit repository is private and the server is reachable only over NetBird, so the key is recorded here with the kit owner’s explicit approval. If this kit repository ever becomes public, move the key to the studio vault (t1k vault) and rotate it. This is not a precedent for other secrets: shared credentials belong in the vault.
Publish a file
Section titled “Publish a file”- Confirm the VPN is up and the server answers (see Troubleshoot).
- In FigCraft, open Preferences and set the server to the address above. Until a server is chosen, the app reports “online sharing is off: choose a server in Preferences”. The menu label was not checked in the UI; look for the server setting in Preferences.
- With the server set, share the open
.figcraftfile from FigCraft’s sharing controls. The exact menu label was not checked in the UI.
Drive the app over MCP
Section titled “Drive the app over MCP”- Start FigCraft with the control port:
figcraft --control 47800. The control port listens on loopback only. - Attach an MCP client to that running app:
figcraft-cli mcp --attach 47800(MCP over stdio). - Registered on the studio machine as:
claude mcp add -s user figcraft -- figcraft-cli mcp --attach 47800. - Gotcha: an app started without
--controlcannot be attached to. It must be restarted, and unsaved work in that session is lost. Save first.
Publish a plugin folder
Section titled “Publish a plugin folder”figcraft-cli plugin publish publishes a plugin folder to a figcraft-server plugin directory. It does not publish a design file. Run figcraft-cli plugin publish --help for its arguments; they were not verified here.
Troubleshoot
Section titled “Troubleshoot”| Symptom | Cause | Action |
|---|---|---|
| DNS or connection failure | VPN is down | Connect NetBird (t1k:vpn) |
| HTTP 502 “Connection Error” from the NetBird reverse proxy, VPN up | The backend figcraft-server is not answering. Observed 2026-11-10: DNS resolved to 10.100.197.50 and the proxy returned 502. | Server-side outage. Tell the server admin. This is not a client fix; do not change local config. |
| “online sharing is off” | No server set in Preferences | Publish step 2 |
| MCP attach fails | App was not started with --control | Restart with figcraft --control 47800 (save first) |
Local reference
Section titled “Local reference”Linux package ai.storyteller.figcraft 0.17.0 ships the binaries figcraft and figcraft-cli. Its README is at /usr/share/doc/figcraft/README.md. That README names three further FigCraft docs (CLI, MCP and control protocol) which are not installed locally.