@higgsfield/video-editor-mcp
v3.0.1
Published
Higgsfield Video Editor for Claude Desktop and Claude Code, as a local MCP server over stdio: edits TSX video projects on this machine with the higgsedit CLI and serves the editor panel.
Downloads
2,655
Readme
Higgsfield Video Editor for Claude
Edit videos with Claude on your Mac. Say what you want: cut the clips, add a title, caption the speech, put music under it, animate the text. The edit opens in the Video Editor panel inside the Claude Desktop chat and updates as you talk. You can scrub, trim and tweak there too. When it is right, export an MP4.
Your footage and projects stay on your Mac. Only image and video generation, if you use it, goes through your Higgsfield account.
Install
You need a Mac with Claude Desktop. Open Claude Code and paste:
Install the Higgsfield Video Editor in my Claude Desktop:
1. Make sure Node.js 22.12+ and ffmpeg are installed. If not, install them with Homebrew (`brew install node ffmpeg`), and ask me before installing Homebrew itself.
2. Run `npx -y @higgsfield/video-editor-mcp@latest setup --claude-desktop --yes`.
3. Run `npx -y @higgsfield/video-editor-mcp@latest doctor` and fix anything it reports as not ok.
4. Tell me to click Install in the dialog Claude Desktop just opened, then start a new chat there (no restart needed) and send the first prompt that setup printed.Claude Desktop shows an install dialog for Higgsfield Video Editor. Click Install, start a new chat and send:
Use the Higgsfield Video Editor to create a vertical video project with an animated title and music, and open it in the editor panel.
Install by hand
You need macOS, Claude Desktop, Node.js 22.12 or newer and ffmpeg (brew install node ffmpeg). Run:
npx @higgsfield/video-editor-mcp setupIt opens Claude Desktop's install dialog for the Higgsfield Video Editor extension. Click Install and start a new chat; no restart needed. Headless Chrome (about 100 MB) downloads on the first preview or export.
--claude-code adds it to Claude Code instead, in the .mcp.json of the current folder (or --dir <path>);
--all does both. --no-open writes the extension (.mcpb) without opening it, and prints where.
To add it to an MCP config by hand, this is the entry (setup writes npx by its full path, so Claude finds it):
{
"mcpServers": {
"higgsfield-use-video-editor": {
"command": "npx",
"args": ["-y", "@higgsfield/video-editor-mcp@latest"]
}
}
}Use it
In a new Claude Desktop chat, try:
- "Use the Higgsfield Video Editor to create a vertical video project with an animated title and music, and open it in the editor panel."
- "Trim the dead air in ~/Movies/trip, caption the interview and add a lower third at 0:06."
- "Export it, then a 1:1 version for the feed."
A project is a folder of its own, anywhere: index.tsx is the edit, media/ holds your footage, exports land in
renders/. The panel serves the folder over localhost, so the home folder itself, ~/Library, system and hidden
folders are refused. New projects from the panel go in ~/Downloads. Set HIGGSEDIT_PROJECT_ROOTS (folders
separated by :) in the server's env to limit projects to those folders; the panel then creates them in the first.
Updates
The entry runs @latest, so each time Claude starts the server it gets the newest version. Nothing to update by
hand.
When something is off
npx @higgsfield/video-editor-mcp doctorchecks Node, ffmpeg, the bundled higgsedit CLI and the panel. In a chat, ask the editor to run its diagnostics.
Remove
In Claude Desktop, open Settings → Extensions and remove Higgsfield Video Editor. Your projects stay where they are.
Under the hood
The package is a local MCP server over stdio. It bundles @higgsfield/higgsedit,
the command-line video editor, and starts higgsedit dev for each open project. That server holds the project,
applies edits to index.tsx by element id, renders frames and MP4s with headless Chrome and ffmpeg, and serves
the editor panel. The chat's tools and the panel talk to the same server, so they share one undo history.
Proprietary: see LICENSE. Bundled open source software and fonts are listed in THIRD_PARTY_NOTICES.md.
