Appearance
Connect AI Assistants
Connect StoryFolder to an AI assistant and you can talk to your footage instead of clicking through it.
Ask which shots are closeups. Ask it to look at the first three shots and tell you what's happening. Ask it to tag twenty shots at once, or start a PDF storyboard while you keep working. It reads the same library you see on screen, and every change it makes is one you can undo.
Setup is one click from inside the app. Open Preferences → MCP Server, or click Connect an AI assistant in the header, pick your assistant, and press the button. StoryFolder works out everything the assistant needs to know about this computer, sets it up, and then checks the assistant's own settings to confirm it worked — so "connected" means it looked, not that it hoped.
Three clients are set up from there:
Claude DesktopOne click in the app, or the double-click extensionClaude CodeOne click. StoryFolder runs the command for youChatGPT CodexOne click, on the ChatGPT account you have
Then restart the assistant. None of them notice a new connection mid-session.
What the panel shows you
It's the same panel whether you open it from Preferences or from the header button, and it tells you where you stand rather than making you guess:
| What it says | What it means |
|---|---|
| Checking whether it's already connected… | Looking at your assistant's settings |
| …is not detected | The assistant isn't installed on this computer — there's a link to its install page |
| … is installed. StoryFolder isn't connected yet. | Ready to go. Press the button |
| Connected | Set up, and confirmed afterwards rather than assumed |
| Added to … — not active yet | Claude Desktop only. Correctly set up; restart Claude to switch it on |
| …points somewhere else on this computer | An older setup, aimed at a folder that has moved. One click repairs it |
It also names the three things it found on this computer — Node, the connector folder, and where your assistant keeps its settings — with their real locations. Anything it couldn't find is said plainly rather than guessed at: a plausible wrong answer here produces a setup that silently never starts.
If you'd rather do it by hand, the panel never hides the manual route: Or run the command yourself… shows the exact command for your machine, ready to copy.
What you can ask for
Here are the kinds of things people actually ask. Things to try has more, with the answers they came back with.
| You say | What you get |
|---|---|
| "What's in my library?" | Your projects, with shot counts and durations |
| "Show me shots 1 to 4 of the hoodie ad" | The actual frames, so it can see them and describe them |
| "Which shots have no Shot Size filled in?" | Every gap in your notes, across one project or all of them |
| "Tag shots 4 through 9 as B-roll" | Written to all six at once, as a single undo |
| "Export a PDF storyboard" | Queued in the background while you keep working |
| "Give me the shot list as a spreadsheet" | An XLSX export with timecodes |
| "What did you change in here?" | The list of its own edits, so you can roll them back |
A few limits worth knowing up front:
- It searches your notes, not the picture. "Find the closeups" works if you have a field where closeups are recorded. If you don't, ask it to look at the frames and fill that field in — then the search works from then on.
- It can see up to twelve frames at a time. A forty-shot video takes a few passes.
- StoryFolder has to be open. The assistant reads the running app, not your files.
Your footage stays on your computer
"AI integration" usually means uploading your media somewhere. This doesn't.
The connection runs on your computer and talks to StoryFolder locally. Your video files are never uploaded. There's no account to make and no key to paste. Close StoryFolder and the whole thing stops working, which is the behaviour you want.
The one thing that does travel is whatever the assistant sends to its own AI service — the same as if you'd typed it into the chat box yourself. So if a shot note is confidential, treat it the way you'd treat anything you paste into a chat. Read-only mode doesn't change this: it stops the assistant writing, not reading.
The technical version
The connector reaches StoryFolder over loopback — 127.0.0.1, the network interface that never leaves the machine. When StoryFolder starts, it writes a small handshake file into your user folder holding the port it picked and a token for that session. The connector reads that file before each request. No StoryFolder is running, no token, nothing works.
Let it read, but not edit
There's a Read-only switch. Turn it on and the assistant can read everything and change nothing — not by accident, not by misunderstanding you, and not by being talked into it. The editing tools aren't hidden from it, they're not offered to it at all.
With read-only on it can still list your projects, read your shots and notes, look at frames, search your library, and check on exports. What it loses is renaming, tagging, adding note fields, importing and exporting.
You'll find the switch during setup on either platform, and you can change your mind later. It's a checkbox, not a commitment.
Every edit is undoable
When the assistant changes something, it goes through the same path the app itself uses. The change lands in StoryFolder's Version history, tagged as made by an assistant rather than by you.
So you can open Version history, see exactly which entries came from the assistant, and roll back those. Tagging twenty shots counts as one entry and one undo, the same as a multi-select edit you make by hand.
You can also ask directly: "what have you changed in this project?"
What you need
- StoryFolder, open. If it's closed, the assistant tells you so in plain words and nothing else happens.
- A desktop assistant. StoryFolder sets up three from inside the app: Claude Desktop, Claude Code, and ChatGPT Codex. This runs on your computer, so a browser tab or a phone can't reach it — and it doesn't appear in the ChatGPT desktop app's own chat window.
- Node 18 or newer, for Claude Code and Codex. Node is a free runtime those two need in order to run the connector, and they don't bring their own copy — StoryFolder finds yours for you, including installs those assistants can't normally see. Claude Desktop's extension needs none of this.
- A couple of minutes.
Check it worked
The panel tells you when it's connected. To prove it end to end, restart your assistant with StoryFolder open, then ask:
What projects are in my StoryFolder library?
You should get your real project names back, with shot counts and durations. If you don't, troubleshooting covers the usual causes.
Not the same thing as AI Autofill
Connecting an assistant is a conversation with your library. AI Autofill is a batch job that looks at frames and fills the metadata fields you enabled — a different feature, with its own plan limits, with different privacy consequences.
Next step
→ Set up Claude Desktop, set up Claude Code, or set up ChatGPT