creator-studio-mcp
AGENTS.md1 starsChanged 6 days agoMITView on GitHub
Two jobs bring an agent here. Pick yours: Don't stop before 1 to 3 are true. Don't claim 4 until someone has seen the result. If Node is missing or older than 22, ask the user, then install the current LTS (brew install node, or the installer from nodejs.org). Set up the assistant you are running in, plus any other the user names. If the user didn't say and several exist, set up all that exist and list them in…
- Installs packages
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 32,671 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
The file
We split this AGENTS.md into the rules it gives an agent
11 rules. About 0 are common, 4 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 6
You are changing this repository: read CONTRIBUTING.md. Run scripts/verify.sh before you commit.
- Very specific: line 15
After the user restarts the assistant, creator_studio_status lists the installed apps and permissions.problems is empty.
- Distinctive: line 17
Don't stop before 1 to 3 are true.
- Very specific: line 21
Every command below runs without prompts.
- Distinctive: line 22
Don't overwrite config you didn't write.
- Very specific: line 24
Ask the user before you install Node.js, Homebrew or ffmpeg.
- Very specific: line 35
If Node is missing or older than 22, ask the user, then install the current LTS (brew install node, or the installer from nodejs.org).
- Very specific: line 49
Use the full npx path in every entry: apps started from the Dock don't see the shell's PATH.
- Distinctive: line 77
If the file isn't valid JSON, the command stops and changes nothing.
- Very specific: line 79
If npx can't find the package (npm returns 404), install from a clone instead: see "Install from a clone" in …
- Distinctive: line 104
Only the user can do these steps.
≈ “Common” is an estimate: at least 1 in 5 of the 41,581 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
For agents
Two jobs bring an agent here. Pick yours:
- The user asked you to install Creator Studio MCP (or "set this up"): follow Install below. Work from any folder; you don't need a clone.
- You are changing this repository: read CONTRIBUTING.md. Run
scripts/verify.shbefore you commit.
Install
Done when
claude mcp listorcodex mcp listshowscreator-studioas connected or enabled, for each assistant you set up. For Claude desktop, the config file has the entry and parses as JSON.- The
studioskill is installed for the same assistants. - You gave the user the hand-off message in step 6.
- After the user restarts the assistant,
creator_studio_statuslists the installed apps andpermissions.problemsis empty. You can't check this in the session that did the install: the user checks it, or the next session does.
Don't stop before 1 to 3 are true. Don't claim 4 until someone has seen the result.
Rules
- Every command below runs without prompts. Never run the plain
npx skills add <repo>without flags: it waits for input. - Don't overwrite config you didn't write. The commands below add one entry and leave the rest alone.
- If your sandbox can't write the config or skill folders (Codex's default sandbox keeps
~/.codexread-only), ask to run the commands from steps 3 and 4 with approval or outside the sandbox. If you can't, give the user those commands, filled in, to paste into a terminal, then continue from step 5 once they have. Don't switch to a clone or write your own install script to get around the sandbox. - Ask the user before you install Node.js, Homebrew or ffmpeg.
- The version is
0.7.1, the version inpackage.json. Use the same version in every command.
1. Check the Mac
uname -s # must print Darwin
node --version # must be v22 or later
command -v npx # note this full path; GUI apps need itIf Node is missing or older than 22, ask the user, then install the current LTS (brew install node, or the installer from nodejs.org).
2. Find the assistants to set up
command -v claude # Claude Code
command -v codex # Codex CLI (the Codex app reads the same config)
ls -d /Applications/Claude.app 2>/dev/null # Claude desktopSet up the assistant you are running in, plus any other the user names. If the user didn't say and several exist, set up all that exist and list them in the hand-off.
3. Add the server
Use the full npx path in every entry: apps started from the Dock don't see the shell's PATH.
Claude Code: first claude mcp get creator-studio. If it exits 0, an entry exists: leave it, or replace it with claude mcp remove --scope user creator-studio if it points at an older version. Then:
claude mcp add --scope user creator-studio -- "$(command -v npx)" -y creator-studio-mcp@0.7.1Codex: this adds the entry to ~/.codex/config.toml, or replaces an existing creator-studio entry:
codex mcp add creator-studio -- "$(command -v npx)" -y creator-studio-mcp@0.7.1Claude desktop: the config is ~/Library/Application Support/Claude/claude_desktop_config.json. This merges one entry, keeps everything else, and saves the old file as .bak:
node -e '
const fs = require("fs"), path = require("path"), [f, npx] = process.argv.slice(1);
let j = {};
if (fs.existsSync(f)) { j = JSON.parse(fs.readFileSync(f, "utf8")); fs.copyFileSync(f, f + ".bak"); }
j.mcpServers = { ...j.mcpServers, "creator-studio": { command: npx, args: ["-y", "creator-studio-mcp@0.7.1"] } };
fs.mkdirSync(path.dirname(f), { recursive: true });
fs.writeFileSync(f, JSON.stringify(j, null, 2) + "\n");
console.log("updated " + f);
' "$HOME/Library/Application Support/Claude/claude_desktop_config.json" "$(command -v npx)"If the file isn't valid JSON, the command stops and changes nothing. Show the user the error instead of rewriting the file.
If npx can't find the package (npm returns 404), install from a clone instead: see "Install from a clone" in skills/studio/references/setup.md. Clone into ~/.local/share/creator-studio-mcp unless the user names a place.
4. Install the skill
Pick the -a values for the assistants you set up (claude-code, codex):
npx -y skills add teemukinos/creator-studio-mcp -g -a claude-code -a codex -yClaude desktop and claude.ai can't install skills from the shell. Tell the user to download studio.zip from the latest release and upload it as a skill in Claude's settings.
5. Check from the shell
claude mcp list # expect: creator-studio: ... ✔ Connected
codex mcp list # expect: creator-studio ... enabledThe first run downloads the package, so it can take a minute. If the entry shows as failed, read Troubleshooting.
The video route also uses ffmpeg (command -v ffmpeg). If it is missing, say so in the hand-off; don't install it without asking.
6. Hand off to the user
Only the user can do these steps. Send them this, with the app names filled in (the "host app" is the app that runs the assistant: Claude, Codex, Terminal, iTerm2 or the editor):
Creator Studio MCP is installed for
<assistants>. Three things only you can do:
- Restart
<assistants>so they load the new server.- Accessibility: in System Settings > Privacy & Security > Accessibility, turn on
<host app>. The menu and dialog tools need it.- Open each Creator Studio app once by hand and click through any welcome or subscription screen. Those screens block automation.
The first time a tool uses an app, macOS asks whether
<host app>may control it: click Allow. Screen Recording is needed only for screenshots.Then ask me to run
creator_studio_status: it lists the apps it found and any permission that is still missing, with where to turn it on.
Update
Change the version in each entry, then restart the assistant:
claude mcp remove --scope user creator-studio
claude mcp add --scope user creator-studio -- "$(command -v npx)" -y creator-studio-mcp@<new version>
codex mcp add creator-studio -- "$(command -v npx)" -y creator-studio-mcp@<new version>For Claude desktop, run the merge command from step 3 with the new version. To update the skill, run the skills add command from step 4 again: it replaces the installed copy.
Uninstall
claude mcp remove --scope user creator-studio
codex mcp remove creator-studio
npx -y skills remove studio -g -yFor Claude desktop, delete the creator-studio entry under mcpServers in ~/Library/Application Support/Claude/claude_desktop_config.json, then restart the app.
Two things stay behind, and both are the user's to delete: the learning ledger in ~/.studio/ and the job folders in ~/Studio/. Ask before removing either. Permissions granted in System Settings stay too; the user can turn them off there.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

