Storytold MCP server
2026년 11월 13일 커밋15개의 로컬 헤드리스 크리에이티브 앱을 Claude Code 및 Codex와 통합하여 AI 기반의 사진, 영상, CAD 및 문서 편집을 지원합니다.
다른 이름 devsolux/storytold
- 스타
- 13
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- —
- 마지막 커밋
- 2026년 11월 13일
- 라이선스
- MIT
Storytold MCP란?
15개의 로컬 헤드리스 크리에이티브 앱을 Claude Code 및 Codex와 통합하여 AI 기반의 사진, 영상, CAD 및 문서 편집을 지원합니다.
프로젝트 README에서 생성된 요약
Storytold MCP server 정보
Storytold를 사용하면 Claude Code 또는 Codex를 통해 사진, 영상 및 CAD 파일을 편집할 수 있습니다. 이 통합 키트는 AI 클라이언트를 오픈 소스 ArtCraft Craft App Suite의 15개 로컬 헤드리스 크리에이티브 애플리케이션과 연결합니다. 원격 게이트웨이를 사용하는 대신, 단일 craft Skill을 사용하여 stdio MCP 등록을 통해 사용자의 기기에서 네이티브 엔진을 직접 구동합니다.
사용자는 Python CLI를 사용하여 특정 애플리케이션 바이너리를 설치, 검증 및 고정함으로써 로컬에서 설정을 관리합니다. 이 시스템은 macOS, Linux, Windows를 지원하여 PhotoCraft, FilmCraft 또는 CADCraft와 같은 각 도구가 호스트에 올바르게 등록되도록 보장합니다. 대부분의 앱은 안전을 위해 특정 읽기/쓰기 루트 내에서 작동하지만, SoundCraft 또는 LightCraft와 같은 특정 도구는 설정 시 명시적으로 승인하면 사용자 전체 파일에 접근할 수 있습니다.
이 설정은 크리에이티브 워크플로우에 대한 로컬 제어권을 유지하려는 개발자와 크리에이터를 위해 설계되었습니다. 초기 플러그인에 바이너리를 포함하지 않는 대신, 요청 시에만 필요한 명령줄 인터페이스를 다운로드하고 조사하는 검증된 프로세스를 제공합니다.
활용 사례
- 1AI 기반 이미지 및 벡터 편집로컬 네이티브 엔진을 사용하여 복잡한 사진 조작이나 벡터 일러스트레이션 생성을 AI 클라이언트에 지시합니다.
- 2문서 및 프레젠테이션 생성 자동화AI 어시스턴트에게 워드 프로세서 문서, 스프레드시트 및 슬라이드 덱을 생성하거나 편집하도록 요청합니다.
- 3로컬 3D 및 모션 그래픽 작업AI를 사용하여 3D 텍스처 페인팅, 절차적 재질 또는 모션 그래픽 효과를 관리합니다.
- 4기술 설계 및 CAD 관리기술 도면을 수정하거나 관리하기 위해 컴퓨터 지원 설계 작업을 AI 클라이언트에 위임합니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
자동 검사
2026년 11월 14일에 실행됨전체 보고서 →아직 인증되지 않았습니다. 서버는 80점 이상의 점수, 심각한 결함 없음, 그리고 검사에 충분한 데이터를 갖추어야 합니다. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능devsolux/storytold is public and reachablegithub.com/devsolux/storytold ↗통과
- 패키지가 이 저장소를 소스로 명시검사되지 않음
- 빌드 출처(Sigstore 증명)검사되지 않음
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-11-13github.com/devsolux/storytold ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음검사되지 않음
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
- 모델에 대한 숨겨진 지침 없음0 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 원격 엔드포인트가 MCP 핸드셰이크에 응답검사되지 않음
README
GitHub에서 보기Storytold
Local creative work. Native app engines. Verified file handoffs.
A Claude Code and Codex plugin for the open-source ArtCraft Craft App Suite:
one craft Skill drives fifteen local, headless Craft MCP apps (photo, vector,
video, RAW, PDF, layout, spreadsheets, documents, slides, CAD, audio, motion,
interface design, procedural materials and 3D texture painting) through staged
copies and verified exports.
Thank you, ArtCraft team! Storytold is built on the Craft App Suite, which the ArtCraft team released as free, open-source software: fifteen creative apps, each written from scratch. We're grateful for their generosity. None of this integration would exist without their work.
❤️ ArtCraft team 💚
Contents
- Overview
- Quick start
- The Craft App Suite
- Setting up the native apps
- Updating and removing
- Where things live
- Working safely
- Development
- Verification status
- Repository map
- License and affiliation
Overview
Storytold is Devsolux's local integration kit for the fifteen existing Craft
CLI MCP servers. One compact craft Skill guides the host; each app keeps its
own schemas, editing state, rendering and save semantics. Deterministic helpers
install and pin the CLIs on explicit command, stage files, generate
evidence-bound configuration and verify artifacts within stated limits.
User + Claude Code / local Codex
│ one craft Skill; native tool discovery and approvals
├── stdio ── PhotoCraft, VectorCraft, FilmCraft, LightCraft
├── stdio ── PdfCraft, EffectCraft, DesignCraft, GridCraft
├── stdio ── WordCraft, DeckCraft, CADCraft, SoundCraft
└── stdio ── FigCraft, MaterialCraft, TextureCraft
│
native engines → durable files
What it is
- One instructional Skill, fifteen on-demand app cards and two workflow guides.
- Fifteen direct, native stdio MCP registrations, one per app and host.
- A standard-library Python CLI (
storytold.py) that installs, verifies, pins, probes and registers the Craft CLIs, but only when you run it.
What it is not
- No gateway MCP server, daemon, router or second AI agent.
- No bundled binaries: installing the plugin adds guidance, the reviewed release manifest and inactive templates, never executables, permissions or running MCP processes.
- No remote ChatGPT connector. Local Codex support is an additive packaging and configuration adaptation.
- No OS sandbox. See Working safely and SECURITY.md.
Quick start
1. Install the plugin. Repository devsolux/storytold, plugin storytold,
marketplace devsolux-storytold. Both hosts take plugin@marketplace:
claude plugin marketplace add https://github.com/devsolux/storytold
claude plugin install storytold@devsolux-storytold
codex plugin marketplace add devsolux/storytold
codex plugin add storytold@devsolux-storytold
2. Install the native apps. From a clone, or from the installed plugin
directory (<home>/plugins/cache/devsolux-storytold/storytold/<version>/ under
~/.claude or ~/.codex), set up one app or all fifteen:
python3 storytold.py setup --app photocraft
python3 storytold.py setup --all --acknowledge-unconfined
3. Start a new host session and use the Skill: /storytold:craft in Claude
Code, or storytold:craft from the Codex Skill picker.
python3 storytold.py doctor reports, per app, the desktop app, CLI and host
registration it finds and prints the exact setup command for anything missing;
the Skill offers the same command in chat when a server is not connected.
The Craft App Suite
ArtCraft Launcher installs the Craft App Suite: free, open-source creative tools from the ArtCraft team, each written from scratch in Rust and each able to stand on its own. The File access column shows how Storytold launches each app's MCP server.
| App | What it's for | File access | Code | Learn more | |
|---|---|---|---|---|---|
| PhotoCraft | Image editing: layers, masks, type and real PSD files | Read/write roots | GitHub | Website | |
| VectorCraft | Vector illustration | Read/write roots | GitHub | Website | |
| FilmCraft | Video editing, color and sound | User-wide | GitHub | Website | |
| LightCraft | Photo library and raw development | User-wide | GitHub | Website | |
| PdfCraft | Reading, organizing and protecting PDFs | Read/write roots | GitHub | Website | |
| EffectCraft | Motion graphics and visual effects | Read/write roots | GitHub | Website | |
| DesignCraft | Page layout and publishing | Read/write roots | GitHub | Website | |
| GridCraft | Spreadsheets and data | User-wide | GitHub | Website | |
| WordCraft | Word processing and documents | Read/write roots | GitHub | Website | |
| DeckCraft | Presentations and slide decks | Read/write roots | GitHub | Website | |
| CADCraft | Computer-aided design | User-wide | GitHub | Website | |
| SoundCraft | Audio recording and editing | Read/write roots | GitHub | Website | |
| FigCraft | Interface design and prototyping | Read/write roots | GitHub | Website | |
| MaterialCraft | Procedural PBR materials as node graphs | Read/write roots | GitHub | Website | |
| TextureCraft | 3D texture painting, baking and PBR export | Read/write roots | GitHub | Website |
- Read/write roots (eleven apps): launched with native root flags that let
them read the workspace and write only its
outputs/directory. PdfCraft also keeps its single--rooton the workspace; both apply. TextureCraft loading a.mcraftpackage startsmaterialcraft-clioutside those roots. - User-wide (four apps): launched without file-root flags, so they can
read and write anything your OS user can.
setupinstalls and registers them only with--acknowledge-unconfined; keep them for non-sensitive work or run them under OS isolation.
Setting up the native apps
Each app's MCP server is its CLI, <app>-cli. Neither the plugin nor the
desktop app provides or registers it, so until it is set up the Skill correctly
reports that the app's native tools aren't connected. setup supports macOS
(universal), Linux x86_64 and Windows x64 and requires Python 3.11+.
What setup does
For each selected app, setup:
- Downloads the archive pinned for your platform in
config/releases.json(the macOS CLI zip, the Linux tarball or the Windows portable zip). - Checks it against that manifest and the release's own
SHA256SUMS.txt, then extracts exactly the one<app>-cli. - Verifies provenance (see Provenance).
- Stages the candidate beside the active install and runs preflight plus the official MCP SDK probe against it: initialize, tools/list and one read-only call.
- Promotes it only then, to
~/.local/opt/craft/bin(or%LOCALAPPDATA%\Storytold\craft\binon Windows), and pins the binary hash in a private lock. - Registers the server with every host CLI on PATH (
codex mcp add,claude mcp add --scope user).
A candidate that fails any step leaves the previous binary, its pin and the
registrations untouched; an upgrade interrupted between the file replace and the
lock rewrite is reconciled by the next run. Re-running setup is idempotent: an
app whose installed binary matches its pin and the manifest is skipped, and a
matching registration is kept. Nothing runs unless you invoke it. Start a new
host session afterwards.
Options
| Option | Effect |
|---|---|
--app <app> / --all |
Select one app (repeatable) or all fifteen. |
--acknowledge-unconfined |
Also install and register the four user-wide apps. Not evidence of isolation. |
--host {codex,claude} |
Register with the named host only (default: every host CLI on PATH); a named host that is not on PATH fails the run. |
--dry-run |
Preview what a real run would do per app (keep, install, upgrade, skip or refuse, a download only where one is needed, each registration) and whether it would pass (exit status 1 if not), or, with --remove, exactly what would be removed. Changes nothing. |
--list |
Show manifest, installed, pinned and registered state, and the paths in use. |
--upgrade |
Move an app whose pin changed to the manifest release. |
--replace |
Re-register a same-name server that points elsewhere; the old entry is restored if the new one cannot be added. |
--remove |
Unregister only the user-scope entries setup itself wrote (same command and arguments, app still pinned) and delete only a binary whose bytes match the lock and that no remaining registration launches, on any host; anything else is reported and left alone. |
--skip-probe |
Register without exercising the binary, and say so. |
--trust-upstream-sums |
Linux/Windows: proceed on the manifest and SHA256SUMS.txt when no Sigstore bundle or cosign is available; recorded in the lock. |
python3 storytold.py setup --help lists the remaining path and timeout
overrides. Other platforms, air-gapped machines and custom pins use the manual
chain in operations: download, lock, preflight, probe,
configure, register.
Provenance
On macOS the binary must be Apple-notarized by the ArtCraft team. Upstream does
not code-sign Linux or Windows builds, so the
daily workflow signs every pinned CLI keyless
with Sigstore cosign under its own GitHub identity
and commits the bundles to config/signatures.json.
On Linux and Windows, setup verifies that bundle with cosign verify-blob
(install cosign first) before installing; macOS verifies it too when cosign is
present. Until a release has a bundle, or without cosign,
--trust-upstream-sums proceeds on the manifest and SHA256SUMS.txt alone and
says so in the lock.
Daily release refresh
The workflow checks every app's latest release each day, rewrites the manifest,
signs new CLIs, rebuilds the plugin, runs the checks and the real setup on
Linux, Windows and macOS runners, and opens one pull request on bot/releases
for review (set the repository variable STORYTOLD_AUTO_MERGE=true to merge
green runs automatically). A run that moves a pin also bumps Storytold's patch
version and writes that release's changelog section; merging publishes the
GitHub release v<version>. Users receive the new pins with the next plugin
update.
Updating and removing
Update
Updating takes two steps. First, update the plugin:
claude plugin marketplace update devsolux-storytold
claude plugin update storytold@devsolux-storytold
codex plugin marketplace upgrade devsolux-storytold
codex plugin add storytold@devsolux-storytold
Codex has no plugin update: marketplace upgrade refreshes the Git snapshot
and running plugin add again installs the newer version from it. A plugin
update brings the Skill, docs and the refreshed release manifest; it never
touches installed CLIs or host registrations, and the plugin directory now
carries the new version number.
Second, move the Craft CLIs. --list shows which pins moved
(manifest_commit_pinned: false); --all --upgrade re-downloads only those
apps, verifies and re-probes them, and leaves registrations as they are:
python3 ~/.codex/plugins/cache/devsolux-storytold/storytold/<version>/storytold.py setup --list
python3 ~/.codex/plugins/cache/devsolux-storytold/storytold/<version>/storytold.py setup --all --upgrade --acknowledge-unconfined
When a release changes an app's launch arguments (WordCraft's root flags in
1.5.0, SoundCraft's in 1.5.2, and DeckCraft's, DesignCraft's, FigCraft's and
PdfCraft's in 1.5.4), add --replace so the differing registration is
re-registered; without it setup reports the difference and leaves it alone.
SoundCraft honours its roots only from 0.7.0, so an older installed SoundCraft
is refused until setup --app soundcraft --upgrade --replace moves it; the
same holds for DeckCraft before 0.8.0, DesignCraft before 0.9.0, FigCraft
before 0.7.0 and PdfCraft before 0.9.0, which refuse the flags.
Remove
python3 ~/.codex/plugins/cache/devsolux-storytold/storytold/<version>/storytold.py setup --remove --all
claude plugin uninstall storytold@devsolux-storytold
codex plugin remove storytold@devsolux-storytold
setup --remove --all first unregisters and deletes the fifteen
Storytold-managed CLIs and their pins. The workspace and its outputs stay, and so
does anything the lock cannot prove Storytold installed. Uninstalling the plugin
alone would leave the servers registered and running.
Install from a source checkout
The generated plugins/storytold/ runtime is committed, so both hosts install
straight from the public repository and nothing is built during installation.
From a source checkout, make install-claude-local or make install-codex-local
installs the local marketplace instead. These targets change host state; builds
and tests never run them. Host packaging and installation sources are recorded
in the source ledger.
Where things live
The plugin directory holds code, docs and the release manifest only. setup
keeps everything it installs outside it, so a plugin update or uninstall can
never delete, downgrade or swap a CLI, and one installed copy serves both hosts.
python3 storytold.py setup --list prints the paths in use.
| Where (macOS/Linux) | Windows | What | Written by |
|---|---|---|---|
~/.codex/plugins/cache/devsolux-storytold/storytold/<version>/, same under ~/.claude |
same under %USERPROFILE% |
The plugin: craft Skill, docs, storytold.py, config/releases.json, config/signatures.json. No binaries. |
codex plugin add / claude plugin install |
~/.local/opt/craft/bin/ |
%LOCALAPPDATA%\Storytold\craft\bin\ |
The fifteen Craft CLIs (photocraft-cli … texturecraft-cli, 9–263 MB each, depending on the app and platform). Both hosts launch these, e.g. …/cadcraft-cli mcp. |
setup |
~/.local/state/storytold/ ($XDG_STATE_HOME/storytold on Linux) |
%LOCALAPPDATA%\Storytold\state\ |
Private state: installations.lock.json (pinned hashes), evidence/ (probe receipts per app), venv/ (official MCP SDK for the probe), setup.json (recorded paths). |
setup |
~/craft-work-storytold/ |
%USERPROFILE%\craft-work-storytold\ |
The workspace: inputs/, outputs/ (exports land here), receipts/. |
setup creates it; the apps fill outputs/ |
~/.codex/config.toml and ~/.claude.json |
same | One user-scope MCP registration per app and host, pointing at the absolute CLI path above. | codex mcp add, claude mcp add --scope user, run by setup |
The complete Unix launch templates under config/ are examples only, not
active host configuration. Real config generation chooses .exe on native
Windows and emits concrete, validated paths rather than relying on environment
expansion behaving identically across hosts. Machine-specific configuration
stays out of packages.
Working safely
Every task follows the same loop:
Inspect → staged copy → native edit → preview → save/export → reopen/verify.
- App cards. The fifteen app cards describe app-specific pitfalls: VectorCraft headless selection, LightCraft library locks, PdfCraft explicit saves, DesignCraft UTF-8 byte offsets, GridCraft typed formulas, FigCraft page-unit coordinates, media timing and offline warnings. They are source-derived hints; the connected binary supplies the operative API.
- Cross-app work. Pass verified files, never another server's in-memory IDs. PhotoCraft can export a PNG for DesignCraft; DesignCraft can export a PDF for PdfCraft. If a stage fails, stop at the last verified artifact. No universal batch transaction, automatic write retry or hidden fallback is promised.
- Confinement. Root flags, the Skill, probe receipts and MCP configuration are not an OS sandbox, and other host shell and file tools need appropriate permissions too. Business use requires the local gates in acceptance and the controls in SECURITY.md.
Development
Python 3.11+ runs the core tools and tests; GNU Make is optional convenience. The default checks and build need no third-party Python packages and no network access.
make check
make test
make build
make verify-build
| Target | Purpose |
|---|---|
make help |
List every target; installs and starts nothing. |
make doctor |
Report installed capabilities without starting hosts or native apps. |
make check |
Validate source, links, identities, catalog, examples and inactive packaging. |
make test |
Run all core tests in an isolated source copy; no network or native binaries. |
make build / make verify-build |
Generate the shared plugin from allowlisted canonical files, then check it for drift. |
make package / make source |
Create the deterministic plugin ZIP and the complete source ZIP, each with a checksum. |
make release |
Ordered checks, core tests and reproducible packaging; no publishing or native acceptance claim. |
make setup / make setup-probe |
Create a local .venv; then, as an explicit network opt-in, install the hash-locked official MCP SDK (mcp==2.3.0). |
make test-sdk |
Exercise the real SDK against a synthetic stdio fixture, not the Craft apps. |
make refresh-releases / make sign-releases |
The network steps the daily workflow runs (signing needs cosign). |
make setup-confined |
Install, pin, probe and register the eleven root-confined apps on this machine. |
make clean |
Remove only marked .build/ and dist/; workspaces and .venv stay. |
Builds and tests never commit, push or install; only the explicitly named
make github-* targets commit or push. The Makefile lists every
target, and CONTRIBUTING.md describes the contribution rules.
Verification status
The offline core suite, the official MCP SDK contract test, strict Claude
manifest validation, and Claude Code and Codex installation with Skill
discovery have been run. setup has installed, probed and Sigstore-verified
all fifteen Craft CLIs on macOS, Linux and Windows runners, and thirteen of them
on a developer Mac as well. That is protocol-level evidence, not native acceptance:
the gates in acceptance remain the operator's to run. The
verification report separates what was executed for
each release from documentary evidence.
Storytold MCP 질문
Storytold에 실제 크리에이티브 애플리케이션이 포함되어 있나요?
아니요, Storytold는 기존 Craft CLI MCP server를 위한 통합 키트이며 바이너리나 실행 파일을 포함하지 않습니다.
지원되는 운영체제는 무엇인가요?
설치 프로세스는 macOS (universal), Linux x86_64, Windows x64를 지원합니다.
앱이 올바르게 구성되었는지 어떻게 확인하나요?
python3 storytold.py doctor를 실행하면 각 앱의 데스크톱 앱, CLI 및 호스트 등록 상태를 확인할 수 있습니다.