ChatCut Agent Plugins: connecting Codex, Claude Code, Grok Bot and Cursor to a video editor

The gap between an AI agent and a video timeline

An agent that can write code still cannot touch a video project. The timeline, the media bin, the caption track and the export settings live in an application the agent has no handle on. ChatCut Agent Plugins exist to close that specific gap for one product: ChatCut. The README states the plugins "connect Codex, Claude Code, Grok Bot, and Cursor to ChatCut so you can edit ChatCut video projects with AI assistance." The audience is narrow and clearly defined. You need a ChatCut account, a ChatCut project you want to edit, and one of four hosts. If any of those three is missing, this repository has nothing to offer you. It is not a general agent framework, not an MCP server you can point at arbitrary tools, and not a video editor. It is a set of host-specific packages whose only job is to make an existing editor reachable from an existing agent.

One MCP endpoint, four host packages

The architecture is visible in the repository layout rather than in prose. There are three plugin directories at the top level, codex/, claude/ and grok/, plus a fourth package called chatcut-desktop-codex-plugin/ that the README describes as "the store-facing, skill-only package that helps Codex install and connect the signed ChatCut Desktop app." Each host directory carries its own metadata file in the format that host expects: codex/.codex-plugin/plugin.json, claude/.claude-plugin/plugin.json and grok/.cursor-plugin/plugin.json. Codex additionally has codex/.mcp.json, the MCP server configuration. All four hosts reach the same hosted endpoint, given in the README as https://api.chatcut.io/api/external-mcp/mcp. That single endpoint is the whole integration surface: the plugins are adapters, and the capability lives behind the MCP server. The skills themselves are not duplicated per host. The README says codex/skills/ contains "host adapters plus direct symlinks to canonical craft skills in apps/agent/.claude/skills/" and that claude/skills/ holds "Claude-specific adapters plus direct symlinks to the same canonical agent skills." Brand assets follow the same pattern: codex/assets/ is "shared with Claude through a symlink." So the per-host directories are thin, and the real content is a shared skill tree that the host packages point at. That is a sensible way to avoid four copies of the same skill definitions, and it is also the most fragile part of the design, since it assumes the install path preserves symlinks and that the canonical tree is present.

Installing the ChatCut plugin and running a first prompt

The README does not give a single install command. It points to per-host instructions instead: chatcut.io/chatgpt for Codex, chatcut.io/claude for Claude Code, and grok/README.md for Grok Bot and Cursor. What the README does document is authentication. The host handles it when the plugin is installed or first used, and the README names the two commands explicitly, one per CLI host. For Codex:

codex mcp login chatcut

For Claude Code:

claude mcp login plugin:chatcut:chatcut

Grok Bot and Cursor users do not get a command. According to the README, they "complete the authorization flow from the host's Plugins screen." Either way you should end up signed in to your ChatCut account against the hosted MCP endpoint. Once that is done, the README's example prompts are the fastest way to confirm the connection is live. It lists five, including `Import this video into my ChatCut project.` and `Export the current project.` A reasonable first run is to open a project you do not mind breaking, ask the agent to import a clip, then ask it to export. The README also frames verification as part of the workflow: the plugin is described as letting you "verify that edits are visible in the editor." That phrasing matters, because it tells you the intended check is visual, in ChatCut itself, not a success message from the agent. If the import prompt returns without the clip appearing in the project, the problem is on the connection or project-access side, not in your prompt wording.

Where the plugin setup breaks, and what the README does not cover

The symlink layout is the first real failure mode. If you install by downloading an archive, or through any tool that dereferences or drops symlinks, codex/skills/ and claude/skills/ can end up as empty directories. The plugin metadata would still load, so the host would report the plugin as installed while the craft skills are missing. Nothing in the README describes a check for this. The second gap is rollback and uninstall. The README documents how to log in and which prompts to try, but it does not document how to remove the plugin, how to revoke the authorization, or what happens to in-flight edits if a session drops mid-export. The third is scope. The README lists what the plugins can do (import media, change a timeline, create motion graphics, generate assets, transcribe audio, add captions, export videos) but gives no limits on file size, project size, concurrent sessions, or which media formats the import path accepts. If you are planning to point this at a two-hour multicam project, the README gives you no basis for expecting that to work. The fourth is that this is the wrong tool if you do not want a hosted dependency. Every capability runs through api.chatcut.io, so an offline edit session or an air-gapped environment is out of scope by construction.

How this differs from a plain MCP server or a skill file

The obvious alternative is to configure the ChatCut MCP endpoint directly in your host and skip the plugin packages entirely. The difference is packaging and discovery. A raw MCP configuration gives the host a server URL and a tool list; it does not give you the per-host metadata, the skill definitions, or the store-facing package that walks Codex through installing and connecting the signed ChatCut Desktop app. The plugin repo bundles those. The second alternative is a skill-only approach, a folder of instructions the agent reads. That is closer to what chatcut-desktop-codex-plugin/ actually is, and the README's own distinction between "host adapters" and "canonical craft skills" shows the two layers are separate concerns. A skill tells the agent how to approach a task; the MCP server is what performs the edit. If your host supports MCP but not plugins, wiring the endpoint manually gets you the capability without the packaging, and you lose the shared skill tree that the plugin directories symlink to.

Maintenance, licensing and what the repository leaves open

The last push to this repository was on 2026-09-17, so the code is current as of that date. There are no releases retrieved, which means there is no tagged version to pin to. If you depend on this, you are tracking the main branch or a commit hash, and you should record which commit you installed, because the symlinked skill tree means a change in apps/agent/.claude/skills/ can alter plugin behaviour without any change in the plugin directories themselves. That is the practical upgrade cost: the packages look stable while the content they point at moves. On licensing, the repository does not state a licence. No LICENSE text is given, and the licence field is unknown. Without a stated licence you have no granted rights to redistribute or modify the code, and the README does not address this. Treat the absence as an open question to raise with the maintainers rather than an assumption in either direction. This is not legal advice; if redistribution matters to your organisation, get the licence clarified before you ship anything built on it.

Editorial conclusion

Adopt it if you already edit in ChatCut and one of the four supported hosts is your daily driver, and verify first that your host actually resolves the symlinked skill directories, because the README lists skills as direct symlinks into apps/agent/.claude/skills/ and a checkout that flattens or drops symlinks will leave the plugin with metadata and no craft skills. Do not adopt it if you need a video editor that works without an account, or if your host is not Codex, Claude Code 2.x, Grok Bot or Cursor. Before trusting it in a real project, run the login command for your host, point the agent at a throwaway ChatCut project, and confirm the edit shows up in the editor.

Frequently asked questions

Official sources

1. ChatCut-Inc/agent-plugin on GitHub
2. Issues
3. README