Edit videos with Codex (ChatGPT)
Codex (the agent inside ChatGPT desktop) speaks MCP. Register PandaStudio with one CLI command, then ask Codex to edit your video. PandaStudio ships its own MCP server inside the app, so there's no system-wide Node install required.
Install PandaStudio + ChatGPT desktop with Codex
PandaStudio from writepanda.ai. ChatGPT desktop from openai.com/chatgpt/download. Codex tool use needs a paid ChatGPT plan (Plus, Pro, Team, or Enterprise).
Launch PandaStudio at least once. The first launch writes a local credentials file the MCP server auto-discovers — there's no token to manage.
Connect Codex from PandaStudio Settings (one click)
Open PandaStudio, go to Settings → Local automation, and click both buttons:
- Install to PATH — puts
pandastudio-mcpon your$PATHso Codex can launch it. - Connect agents → Codex → Connect — registers PandaStudio as an MCP server in
~/.codex/config.tomlfor you. No terminal, no JSON editing.
You can also click Install Skill in the same panel — it copies the official PandaStudio Skill into Codex (and Claude / OpenClaw / Hermes) so the agent knows what to do, not just how to call it.
Prefer the terminal? codex mcp add writepanda -- pandastudio-mcp (needs npm install -g @openai/codex first if the codex CLI isn't installed). Windows users with the NSIS installer get pandastudio-mcp on %PATH% automatically.
Ask Codex to edit your video
Open ChatGPT desktop, start a new chat, and pick Codex as the agent. Then try:
- "Open my latest recording, transcribe it, remove filler words and silences, then export an MP4."
- "Create a new 9:16 project, import the file at ~/Recordings/launch.mov, add bold captions, and preview it."
- "List all my projects from this week and tell me which one is longest."
Codex picks PandaStudio's tools out of its MCP registry and drives the editor. You stay in the chat; PandaStudio stays open so you can scrub or tweak by hand any time.
Troubleshooting
- "codex: command not found" — install the Codex CLI:
npm install -g @openai/codex. Then re-run thecodex mcp addcommand from step 3. - "pandastudio-mcp: command not found" — the launcher symlink from step 2 isn't in place. Verify the install:
which pandastudio-mcp. On macOS make sure/usr/local/binis on your PATH (it is by default in zsh and bash). - PandaStudio doesn't appear in Codex's tool list — check the registration with
codex mcp list. Ifwritepandais there but reports errors, runcodex mcp test writepandafor diagnostic output. Most common cause: PandaStudio hasn't been launched yet, so the local credentials file doesn't exist. - No PandaStudio installed (CI, server)? — You can still register the npm-published server, which spawns under your system Node:
codex mcp add writepanda -- npx -y @writepanda/mcp. Functionally identical, just slower to start and requires Node 18+ on PATH. - Prefer editing the config directly? — Codex stores MCP servers in
~/.codex/config.tomlas TOML. The block written bycodex mcp addlooks like[mcp_servers.writepanda]withcommand = "pandastudio-mcp". You can edit it there if you need to scope by project or pin a version.