Skip to content

Set up Claude Code

Claude Code is Anthropic's command-line assistant — a different product from Claude Desktop. If you use both, set up both; they keep separate configurations.

StoryFolder connects it for you. You don't need to find Node, find the connector, or type a command.

What you'll need

  • Claude Code installed, and available as claude in a terminal. If it isn't installed yet, StoryFolder says so and links you to Anthropic's install page.
  • StoryFolder installed and open.
  • Node 18 or newer. Claude Code runs the connector with Node and doesn't bring its own copy. StoryFolder finds it for you — including a version-manager Node under your home folder, which a command line launched from the Dock normally can't see.
  • The connector folder, if you're running the installed app. See where the connector comes from below.

Connect it

  1. Open StoryFolder and go to Preferences → MCP Server, or click Connect an AI assistant in the header.
  2. Choose Claude Code.
  3. StoryFolder shows what it found on this computer — Node, the connector, and where Claude Code keeps its settings. Anything it couldn't find is named, not guessed.
  4. Decide whether you want Read-only. It's a checkbox, off by default. More below.
  5. Click Install StoryFolder MCP.
  6. Restart Claude Code. It won't pick up a new connection mid-session.

StoryFolder runs claude mcp add for you with the real locations filled in, then checks Claude Code's own settings to confirm it took. "Connected" means it looked.

It sets the connection up for your whole account, so it's there in every folder you work in — not just the one Claude Code happened to start in.

Check it worked

With StoryFolder open, start a Claude Code session and ask:

What projects are in my StoryFolder library?

You should get your real project names back, with shot counts and durations. Then try something more interesting.

Let it read, but not edit

Tick Read-only before you connect and Claude Code can look at everything and change nothing. Renaming, tagging, adding note fields, importing and exporting stop being offered to it.

To change your mind, tick or untick the box and connect again — it replaces the earlier setup. Restart Claude Code afterwards.

There's more on what read-only costs you, and what it doesn't protect against, on the overview.

Where the connector comes from

In a packaged StoryFolder install, the connector is a folder you download once and keep.

Download Codex Extension

Version 0.3.0 · For Codex on macOS, Windows and Linux

  1. Download the file above and unzip it.
  2. Move the folder somewhere permanent — ~/StoryFolder-connector, say. Not Downloads, which you'll empty one day.
  3. Reopen the MCP Server panel. StoryFolder looks in your home folder, Downloads, Desktop, Documents and Applications for it.

If it still can't find it, use Locate connector folder… in the panel and pick the folder yourself. StoryFolder only accepts a folder that actually holds the connector — one containing src/index.js and our manifest.json — so a wrong pick is refused rather than silently registered.

It's the same download as Codex uses

One connector folder serves Claude Code and ChatGPT Codex. You don't need two. Claude Desktop's .mcpb extension is a different file.

If you'd rather run the command yourself

The panel never hides it. Click Or run the command yourself… and it shows the exact command, already filled in with this computer's paths:

bash
claude mcp add storyfolder --scope user -- /absolute/path/to/node /path/to/StoryFolder-connector/src/index.js

With read-only:

bash
claude mcp add storyfolder --scope user \
  --env STORYFOLDER_MCP_READ_ONLY=1 \
  -- /absolute/path/to/node /path/to/StoryFolder-connector/src/index.js

Confirm it registered:

bash
claude mcp list

Use the absolute path to Node

Typing plain node works only if Claude Code can find the same Node your shell does. If yours is managed by nvm, fnm, asdf or volta, it usually can't — use the output of which node. This is exactly the guesswork the in-app button exists to remove, which is why the command it writes always spells the path out.

The panel also shows the same connection as a ~/.claude.json entry, if you'd rather edit that file by hand. Add the object under its top-level mcpServers key.

Next step

Things to try