ChatCut Agent Plugins: Editing Video Projects Through Codex, Claude Code, and Grok Bot
Plugin for agents to interact with Chatcut
At a glance
- What is it?
- ChatCut Agent Plugins connect five AI coding environments (Codex, Claude Code, Grok Bot, Cursor, and Kimi Work) to the ChatCut video editor via a hosted MCP endpoint, letting you import media, edit timelines, generate assets, transcribe audio, and export videos through natural language prompts. The plugin requires a ChatCut account and is structured as one package per agent host.
- Who is it for?
- ChatCut Agent Plugins suit developers and creators who already use Codex, Claude Code, Grok Bot, Cursor, or Kimi Work and want to control their ChatCut video projects through prompts in those environments. They are not useful without a ChatCut account and access to a live project.
- Can I use it commercially?
- Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
- Is it still maintained?
- Yes. The repository last received commits 1 day ago.
- What is it written in?
- Mainly JavaScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on October 1, 2026, and from our analysis. They are not legal advice.
Editorial analysis
What ChatCut Agent Plugins Do and Who They Are For
ChatCut is a video editing platform. Its agent plugins extend five AI coding environments to control ChatCut video projects through natural language: Codex, Claude Code, Grok Bot, Cursor, and Kimi Work. Instead of switching to the ChatCut interface to perform an edit, a user working in one of those environments can type a prompt and have the agent carry out the action.
The README describes the following operations as available through prompts: importing media into a project, changing the project timeline, creating motion graphics, generating assets, transcribing audio, adding captions, exporting videos, and verifying that edits are visible in the editor. This covers a broad range of video production tasks.
The target user is a developer or creator who spends significant time in an AI coding environment and manages video content alongside code-adjacent work. An editor who works exclusively in a video editing GUI has no reason to use this plugin; the value is in reducing context switching for people whose workflow already centers on an AI agent.
Supported Agent Hosts and Package Structure
The repository provides one package per agent host. The codex/ directory contains the Codex plugin package. The claude/ directory contains the Claude Code plugin package. The grok/ directory contains the Grok Bot and Cursor plugin package, since both use the same plugin format. The kimi/ directory contains the Kimi Work plugin package, which the README notes includes mandatory basics, core craft skills, and in-app browser adapters, with a migration guide in its own README.
A fifth directory, chatcut-desktop-codex-plugin/, is a store-facing, skill-only package that helps Codex install and connect the signed ChatCut Desktop app. This is separate from the main Codex plugin.
Package metadata lives in format-specific configuration files: codex/.codex-plugin/plugin.json, claude/.claude-plugin/plugin.json, and grok/.cursor-plugin/plugin.json for Grok Bot and Cursor. The MCP server configuration for Codex is in codex/.mcp.json. Skills in codex/skills/ and claude/skills/ are a mix of host-specific adapters and symlinks to canonical craft skills shared between packages.
Authentication: Connecting Your ChatCut Account via MCP
The plugin connects to ChatCut through a single hosted MCP endpoint:
https://api.chatcut.io/api/external-mcp/mcpThe host handles authentication when the plugin is first used. For Claude Code, authentication runs with:
claude mcp login plugin:chatcut:chatcutFor Codex, the equivalent command is:
codex mcp login chatcutGrok Bot and Cursor users complete the authorization flow from the host's Plugins screen rather than through a CLI command. After authentication, the plugin connects your ChatCut account to the agent session.
The README points to install guides per host: chatcut.io/chatgpt for Codex, chatcut.io/claude for Claude Code, and docs/claude-code-install.md for Claude Code's agent-executable install path. The Grok Bot and Cursor guide is in grok/README.md within the repository.
Working With Video Projects Through Prompts
After installation and authentication, video editing operations become natural language commands in the agent host. The README provides these example prompts:
- Import this video into my ChatCut project. - Add a simple motion graphic overlay. - Generate a voiceover and background music. - Transcribe this clip and add captions. - Export the current project.
Each prompt triggers the agent to call the appropriate ChatCut operation via the MCP endpoint. The plugin also supports verifying that edits are visible in the editor, which allows the agent to confirm that a requested change took effect before proceeding to the next step.
The README does not document which operations are available when the ChatCut account is on a free tier versus a paid plan. Users who hit capability limits should check chatcut.io for plan-level restrictions.
Skill Files and the Canonical Craft Skill Architecture
The repository uses a skill architecture that separates host-specific adapters from canonical functionality. In codex/skills/ and claude/skills/, some files are direct symlinks to canonical craft skills in apps/agent/.claude/skills/. This means that when a core skill is updated, both the Codex and Claude Code packages pick up the change without separate edits.
The .agents/ and .claude-plugin/ directories at the repository root suggest the plugin itself uses skill-file conventions compatible with both the Codex and Claude Code plugin formats. The plugin.json files contain the metadata that each agent host reads to register the plugin.
Shared assets (icons and brand assets) live in codex/assets/ and are made available to the Claude package through a symlink rather than duplicate files.
This architecture keeps the canonical craft skills as a single source of truth across host packages. Adding a new operation means updating the canonical skill file; the change then propagates to all host adapters that symlink it.
Limitations and When to Use the Native ChatCut Interface Instead
The plugin requires both a ChatCut account and access to a specific project. There is no offline mode and no way to use it without a live ChatCut session backing the MCP endpoint. Operations are routed through chatcut.io/api, so network availability and the API's uptime affect every editing action.
For users who do not already work in Codex, Claude Code, Grok Bot, Cursor, or Kimi Work, the plugin adds setup overhead without obvious benefit. The native ChatCut interface is the direct alternative: it provides visual, point-and-click access to the same project operations, does not require MCP configuration, and is available immediately after creating a ChatCut account. Users who are comfortable in a GUI and have no particular reason to prompt-drive their editing should use the interface directly.
The repository has no explicit open-source license listed. Teams with legal requirements around third-party code should treat the absence of a license as 'all rights reserved' under default copyright law, and contact ChatCut before incorporating or redistributing any part of the plugin code.
The last push to the repository was on 2026-09-17.
Editorial conclusion
ChatCut Agent Plugins suit developers and creators who already use Codex, Claude Code, Grok Bot, Cursor, or Kimi Work and want to control their ChatCut video projects through prompts in those environments. They are not useful without a ChatCut account and access to a live project. Before installing, confirm which agent host you are running (the plugin packages are not interchangeable) and check chatcut.io for the current installation guide, which the README explicitly points to for each host.
Frequently asked questions
What is the difference between an agent plugin and a skill in ChatCut's system?
In the ChatCut repository, a plugin is the host-level package that registers the integration with an agent environment (Codex, Claude Code, Grok Bot, Cursor, or Kimi Work). A skill is an individual capability file inside the plugin that defines a specific operation, such as importing media or exporting a project. Skills can be shared across plugins via symlinks to canonical files in the repository.
Does the ChatCut agent plugin work with Claude Code's desktop app?
Yes. The README states that the Claude Code plugin targets Claude Code 2.x and works with both the CLI and the desktop app. The agent-executable install path is documented in docs/claude-code-install.md within the repository.
What ChatCut account is required to use the plugin?
The README lists a ChatCut account and access to a ChatCut project as requirements. It does not specify a particular account tier. Users who reach capability limits within their plan should check chatcut.io for details on what each tier supports.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/chatcut-inc-agent-plugin)