ArtCraft Command Bridge
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
artcraft-command-bridge
One MCP server for the 19 ArtCraft Crafting Apps — 5 tools instead of 978.
artcraft-command-bridge is an MCP server that drives the installed ArtCraft
CLIs. It is a bridge, not an installer or updater: install and update the
apps with the ArtCraft Launcher (or their standalone installers), then let this
server expose them to your agent through five tools.
Each Crafting App ships its own MCP server that turns every engine command into a separate tool. With all 19 apps installed that is 978 tools / 773.1 KB of schema ≈ 198k tokens of permanently resident context, re-sent on every request. This bridge keeps the same command registries behind a directory and a dispatcher:
978 tools · 773.1 KB · ~198,000 tokens → 5 tools · 4.8 KB · ~1,200 tokensSchema measured on 2026-11-12 with all 19 apps installed on Windows.
Why this exists
MCP clients register a server's tool list in full. The protocol has no
"just give me the names, fetch the schema on demand" mode — the client calls
tools/list once and keeps every tool's name + description + inputSchema
in the system payload forever. Some clients have an on-demand tool search
facility, but that covers deferred tools (cron, integrations), not MCP server
tools.
The Crafting Apps already share one model that is perfect for this:
commands— lists stable command IDs with their parametersrun/batch— executes those IDs
Measured across the 19 apps on 2026-11-12, that is 9878 command IDs. The 978 tools the apps' own MCP servers expose are only a subset view of the same registry. So the tools do not need to be flattened into 978 separate entries — they need to be a directory and a dispatcher, which is what this is.
Only PdfCraft ships an on-demand mode of its own (pdfcraft-cli mcp --compact,
which exposes a core set plus tool_search/tool_call); the other eighteen
have no equivalent --compact mode, so there was no unified switch to simply
turn on.
Related MCP server: MCPico
Quick start
1. Install the apps
Install the apps you need — see getartcraft.com/apps.
The recommended path is the ArtCraft Launcher, which installs every app and keeps
them updated. Each app installs a <app>-cli binary.
The bridge does not install or update them. Updating an app only invalidates its registry cache; it does not change the bridge code.
2. Register the server
OpenCode (~/.config/opencode/opencode.json):
{
"mcp": {
"servers": {
"artcraft-command-bridge": {
"type": "local",
"command": ["node", "D:/path/to/artcraft-command-bridge/server.js"],
"enabled": true
}
}
}
}Other MCP clients (mcpServers):
{
"mcpServers": {
"artcraft-command-bridge": {
"type": "stdio",
"command": "node",
"args": ["/absolute/path/to/artcraft-command-bridge/server.js"]
}
}
}Or install the package globally:
npm install -g artcraft-command-bridgeThe npm package includes skills/artcraft/SKILL.md; copy or link that directory
to the skill location used by your MCP client when the client does not discover
package skills automatically.
3. Restart and verify
Restart the client so the tools load. Then call artcraft_apps: it lists all
19 app entries and installed_count reports how many are present on this
machine.
The 5 tools
Tool | What it does |
| Compact installed/missing list by default; |
| List command IDs or describe exact IDs. List mode returns IDs only; parameter strings are capped. Cached locally. |
| Execute commands in order. Compact results, truncated output, base64 redaction, optional preview. |
| Escape hatch — run any CLI subcommand verbatim, with output truncation and image preview. |
| An app's own |
Token efficiency
The default path is optimized for context:
artcraft_commandsstarts in list mode (defaultlimit:10, IDs only). A filter with at most 3 matches returnsparams; broader matches stay compact. Passids:[...](max 6) for commands you will run. Parameter strings are capped at 2,400 chars by default.artcraft_runomits rawstdoutwhen parsedresultsexist. Setinclude_stdout:trueto keep it. Raw output is capped at 6,000 chars and structured results at 8,000 chars; full streams/results go to temp files.Long base64/image strings are replaced with a compact
omitteddescriptor.Image previews are off by default. Set
preview:"auto"or"image"for visual verification; at most one image is attached. Images over 1,024px or 4MB are rejected with a warning so a smaller preview can be exported.MCP text content is compact JSON. The duplicate
structuredContentpayload is off by default; setARTCRAFT_STRUCTURED=1only when a client requires it.
The 19 apps
App | Pick it for |
| Registry |
PhotoCraft ( | Pixel editing, layers, masks, PSD |
|
|
LightCraft ( | RAW development, culling, variants |
|
|
VectorCraft ( | Logos, icons, paths, print vector |
|
|
AniCraft ( | 2D vector animation, tweens, timelines, GIF |
|
|
FigCraft ( | UI screens, components, prototypes |
|
|
DesignCraft ( | Multi-page print, master pages, PDF/X |
|
|
GridCraft ( | Spreadsheets, formulas, charts |
|
|
SoundCraft ( | Audio editing, podcast, mix/master |
|
|
DeckCraft ( | Slide decks, pptx |
|
|
WordCraft ( | Long-form documents, docx |
|
|
CADCraft ( | 2D CAD drafting, dimensions, DXF/DWG |
|
|
SolidCraft ( | 3D solids, STEP drawings, STL/OBJ export |
|
|
EffectCraft ( | Motion graphics, keyframes, comps |
|
|
FilmCraft ( | Video timeline, cuts, captions, MP4 |
|
|
TextureCraft ( | 3D texture sets, painting, baking |
|
|
MaterialCraft ( | Procedural PBR materials, node graphs |
|
|
PdfCraft ( | PDF merge/split, forms, OCR, redact |
|
|
MailCraft ( | Email, contacts, calendar, mailbox files |
|
|
Craft Anything ( | Understanding an unknown binary/app/site |
|
|
Style reference:
cmd-params --cmd <id> --params <json> PhotoCraft, VectorCraft
cmd-inline-eq --cmd <id>={<json>} DesignCraft, GridCraft, SoundCraft,
DeckCraft, WordCraft, MailCraft
cmd-inline-sp --cmd '<id> <json>' CADCraft
positional <id> <json> LightCraft, EffectCraft
script-json run <script.json> FigCraft, SolidCraft
({command, params})
script-json-cmd run <doc> <script.json> AniCraft ({cmd, params})
script-jsonl run <script.jsonl> FilmCraft ({id, params})
batch-json batch <script.json> TextureCraft, MaterialCraft
({open, steps, save})
tool-script run --script steps.json PdfCraft ({tool, args})
cli-only <tool> [args] Craft Anything (one subcommand
per tool, no run form)Registry notes:
commands --jsonis the preferred shape.CADCraft/DesignCraft treat
--jsonas a filter and return[]; MaterialCraft rejects it as an unknown option. The bridge falls back to plaincommands.AniCraft reads
--jsonas a flag that wants a value and errors out; its plaincommandsalready prints JSON.DeckCraft/SoundCraft/TextureCraft print plain-text tables.
PdfCraft has no
commands; the bridge normalizes itstoolslist.Craft Anything names the tool id
command, the titletitleand the summarysummary; the bridge maps them ontoid/label/description.MailCraft writes results to stdout only with
--print; the bridge adds it.
Craft Anything is a different shape
Craft Anything is not a commands + run engine. It is an agent front-end
whose every tool is its own subcommand (core-target-open,
core-session-show, …), so there is no script to hand the bridge.
The bridge therefore treats it as cli-only:
artcraft_commandsgives the directory of its 323 tools — id, title, summary and toolset.artcraft_cliruns one tool verbatim, e.g.{"app":"craft-anything","args":["core-session-show","--format","json"]}.artcraft_runrefuses it and points at the escape hatch.
Per-tool options are not in the registry; read them with
artcraft_help and args:["core-target-open","--help"]. Which tools are usable
depends on the installed engines and the Clean room / Deep mode — ask
artcraft_cli with args:["capabilities"].
Examples
// list matching IDs only (broad query; keeps params out of context)
{ "app": "figcraft", "filter": "node", "limit": 10 }
// get full params for the commands you will run
{ "app": "figcraft", "ids": ["node.create"] }
// build a frame
{
"app": "figcraft",
"steps": [
{ "id": "node.create", "params": { "type": "frame", "name": "Hero", "width": 1200, "height": 800 } }
],
"output": "D:/out/hero.figcraft"
}
// export it (not a command ID — use the escape hatch); preview attaches the PNG
{
"app": "figcraft",
"args": ["export", "hero.figcraft", "-o", "hero.png", "--format", "png", "--node", "Hero"],
"preview": "auto"
}
// draw on the animation stage and save the document
{
"app": "anicraft",
"steps": [
{ "id": "draw.rect", "params": { "x": 10, "y": 10, "w": 80, "h": 40 } }
],
"output": "D:/out/scene.anicraft"
}
// paint a texture set and save the native project (batch-json style)
{
"app": "texturecraft",
"steps": [
{ "id": "layer.add.fill", "params": { "name": "Base", "color": "#c94f3d" } }
],
"output": "D:/out/armor.tcraft"
}
// build a procedural material package (batch-json style)
{
"app": "materialcraft",
"steps": [
{ "id": "graph.seed", "params": { "seed": 7 } }
],
"output": "D:/out/brick.sbs"
}
// model a solid and export it as a mesh
{
"app": "solidcraft",
"steps": [
{ "id": "sketch.create", "params": { "plane": "XY" } }
],
"output": "D:/out/part.stl"
}
// Craft Anything: one tool, one subcommand
{
"app": "craft-anything",
"args": ["core-session-show", "--format", "json"]
}Registry cache and updates
artcraft_commands does not spawn the CLI on every call. The first read of an
app pulls its registry once and writes it to a per-machine cache; later reads
are served from disk. The cache key is the CLI's path + mtime + size, so
updating an app invalidates its entry automatically.
artcraft-sync-registry # installed global CLI
node tools/sync-registry.js # or from a checkout
node tools/sync-registry.js --check # only fill missing/stale entries
node tools/sync-registry.js --app figcraft pdfcraft
node tools/sync-registry.js --clear # delete the cachePass refresh: true to artcraft_commands to re-read one app. Override the
location with ARTCRAFT_CACHE_DIR; the default is
%LOCALAPPDATA%\artcraft-command-bridge\registry on Windows,
~/Library/Caches/artcraft-command-bridge/registry on macOS, and
$XDG_CACHE_HOME/artcraft-command-bridge/registry (or ~/.cache/...) on Linux.
A cache hit removes the CLI process from discovery, but it does not shrink the
response: the token cost is the returned command list, not where it was read
from. Use filter and limit to keep that list small.
Registries have outgrown a small capture buffer — VectorCraft ships ~829 KB of JSON, PhotoCraft ~428 KB, SolidCraft ~397 KB. The bridge reads each registry in full, and a read that fails to parse is never cached, so a broken read cannot freeze an app at "no commands" until its binary changes.
After installing or updating an app
The registry cache handles CLI changes automatically. The app catalog is
loaded when the bridge starts, so restart the MCP client after adding or
removing an app. Then call artcraft_apps: it lists all 19 entries and
installed_count reports how many are present. If an old list persists, check
which server.js the client launches — the process command line should point
at this checkout, not an old copy.
Finding the CLIs
artcraft_apps reports what it found. The bridge probes, in order:
ARTCRAFT_<APP>_CLI— e.g.ARTCRAFT_PHOTOCRAFT_CLI=/opt/craft/photocraft-cliARTCRAFT_HOMEand the official per-OS app roots (%LOCALAPPDATA%\storytold\apps,~/.local/share/storytold/apps,~/Library/Application Support/storytold/apps)PATH(<app>-cli)System install locations (
C:\Program Files\<App>Craft\,/Applications/<App>Craft.app/Contents/MacOS/,/usr/local/bin)
Two apps do not use the plain <App>Craft folder on Windows: AniCraft installs
to C:\Program Files\ArtCraft\AniCraft\ and Craft Anything to
C:\Program Files\Craft Anything\. Both are probed.
Apps that are not installed are reported as such and skipped — the bridge never fails as a whole because one app is missing.
Scope and limitations
19 Crafting Apps. Eighteen are driven by the
commands+run/batchmodel. Craft Anything is command-driven too, but every tool is its own subcommand, so it is exposed as a directory plus the escape hatch rather than throughartcraft_run.The bridge does not install, update, or launch GUI apps. Use the ArtCraft Launcher or the apps' installers for that.
MailCraft and SolidCraft are not on the public app list yet. They are installed by the Launcher on some machines and are wrapped here so the bridge can drive them; on a machine without them they are simply reported as missing.
input/outputsupport varies:both: PhotoCraft, VectorCraft, SoundCraft, FilmCraft, FigCraft, EffectCraft, TextureCraft, MaterialCraft, AniCraft, MailCraft, SolidCraft
run/file output: DesignCraft, GridCraft, DeckCraft, WordCraft, CADCraft
image output: PdfCraft (
--outfor render/image tools)requires CLI-specific import/export flow: LightCraft
Craft Anything: no run form — use
artcraft_cli
TextureCraft / MaterialCraft use a batch JSON script.
outputsaves the native project (.tcraft/.sbs); export PNG/EXR maps withartcraft_cli export.AniCraft takes the document first (
run <file|--sample> <script.json>). Withoutinputit runs on the sample animation. Its script entries are{cmd, params}.SolidCraft saves the native design (
.sc) foroutputending in.sc, and exports a mesh (STL/OBJ/3MF) for any other extension.
Why not an existing tool?
eznix86/mcp-gateway (MIT) — a general-purpose gateway with the same idea, but it aggregates MCP servers, so the Crafting App servers still have to be running as upstream processes, and its
searchis text-similarity rather than an exact registry lookup.ai-2070/claude-storytold-skills (MIT) — a Claude Code plugin whose per-app skills use grep over generated reference catalogs. Same goal, different layer: it still registers every app's MCP server with
claude mcp add, so the tool schemas stay resident.smyrgeorge/artcraft-toolbox (Apache-2.0) — a suite manager (install, verify, update, launch). It is complementary: the toolbox gets the apps onto your machine, this bridge makes them pleasant to drive.
Development
npm test # adapters + bounded I/O + MCP + token tests
npm run test:adapters # per-app argv and temp-file safety
npm run test:exec # streaming capture and UTF-8
npm run test:output # native/export file creation
npm run test:registry # cache miss then cache hit
npm run test:token # list/describe, truncation, base64, preview
node tools/sync-registry.js # pull command registries into the local cache
node tools/probe-mcp.js # probe every app's MCP handshake + tool count
node tools/schema-size.js # measure schema weight, refresh registry snapshots
node tools/agg-test.js # end-to-end self-test of the bridge
node tools/per-app-verify.js # verify each app's run argv is accepted
node tools/cursor-launch-check.js # start the bridge the way a client wouldZero runtime dependencies; Node ≥ 18.
Design notes: token optimization plan (implemented).
License
MIT — see LICENSE. See NOTICE for trademark attribution. The Crafting Apps themselves are open source (MIT OR Apache-2.0) and are developed at github.com/storytold.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Find, vet, and run MCP tools through a secure audited gateway with prompt-injection risk scoring
214 tools for AI agents over one MCP endpoint: image, video, audio, 3D, data, storage, mail, GPUs.
The OpenRouter for tools. One MCP connection gives any AI agent 254 hosted tools, pay per call.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceAggregates tools from multiple upstream MCP servers and exposes them through 4 meta-tools, enabling LLMs to discover and use hundreds of tools without loading all schemas upfront.174 PyPI3Apache 2.0
- FlicenseNot gradedqualityCmaintenanceMCP proxy that bundles flat tool lists into hierarchical subcommand groups to reduce context token usage, supporting multi-server aggregation and auto-generated help from tool schemas.-
- AlicenseNot gradedqualityBmaintenanceMCP proxy that bundles flat tool lists into hierarchical subcommand groups, reducing context token usage and improving tool discovery.19 npm9MIT
- AlicenseCqualityBmaintenanceEnables AI agents to discover and invoke native ArtCraft application capabilities over stdio MCP, creating and editing documents, saving editable projects, and exporting deliverables across supported apps.12MIT