Palmier Pro: A macOS video editor that puts AI agents on the timeline
macOS video editor built for AI. Integrates with your agents Connects your Claude/Codex/Cursor via MCP, or use the in-app agent to work on the same project together.
At a glance
- What is it?
- Palmier Pro is a Swift-native macOS video editor that exposes an MCP server so Claude, Codex, or Cursor can edit your project directly. The catch: only versions through v0.7.6 are open source under GPLv3, and later releases are proprietary.
- Who is it for?
- Adopt Palmier Pro if you are a macOS 26 Apple Silicon user who wants a video editor where AI agents can manipulate the timeline directly, and you are comfortable with the licensing split: source through v0.7.6 is GPLv3, but later binaries are proprietary. Do not adopt it if you need open source guarantees beyond v0.7.6 or if you require Windows or Intel Mac support.
- Can I use it commercially?
- Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository last received commits 6 days ago.
- What is it written in?
- Mainly Swift, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 14, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
What Palmier Pro is and who it targets
Palmier Pro is a video editor for macOS that is built from scratch in Swift. The stated reference point is Premiere Pro, but the differentiator is AI integration. The README says the editor has built-in generative AI for video and images using models like Seedance, Kling, and Nano Banana Pro, all inside the timeline. The target user is someone who already works with AI agents like Claude, Codex, or Cursor and wants those agents to act on a video project, not just on code. This is not a casual consumer tool. It requires macOS 26 (Tahoe) on Apple Silicon, so it is aimed at users on the latest Apple hardware and OS. The project is from Palmier, Inc., a Y Combinator company, which suggests a commercial intent, even though the early source was open.
The mechanism: an MCP server on localhost
The core technical mechanism is an MCP (Model Context Protocol) server that the app exposes when it is open. The server listens at http://127.0.0.1:19789/mcp over HTTP. This is how external agents like Claude Code or Codex can connect. The README gives explicit commands: for Claude Code, you run claude mcp add --transport http palmier-pro http://127.0.0.1:19789/mcp. For Codex, you run codex mcp add palmier-pro --url http://127.0.0.1:19789/mcp. For Cursor, you either use the in-app help menu or manually add a JSON entry to ~/.cursor/mcp.json. There is also a bundled tool called mcpb that allows a one-click install for Claude Desktop. The data flow is straightforward: the app runs a local HTTP server, agents send MCP requests to it, and the server presumably translates those into timeline edits. The README does not detail the exact operations the MCP server supports, but the connection method is concrete and testable.
Getting it running: commands and config keys
To use Palmier Pro, you first download the DMG from the releases page. The README links to a direct download at https://github.com/palmier-io/palmier-pro/releases/latest/download/PalmierPro.dmg. After installing, you open the app, which starts the MCP server. Then you connect your chosen agent. The commands are specific: for Claude Code, claude mcp add --transport http palmier-pro http://127.0.0.1:19789/mcp. For Codex, codex mcp add palmier-pro --url http://127.0.0.1:19789/mcp. For Cursor, you can use the app's Help menu to install automatically, or you can edit ~/.cursor/mcp.json with a JSON block that specifies the server type as http and the URL. For Claude Desktop, the README says to use the bundled mcpb for a one-click install via the Help menu. There is no mention of a CLI or a headless mode. The app must be open for the server to be available, which is a real constraint if you want agents to work while the editor is closed.
A genuine limitation: the licensing split
The most significant limitation is not technical but legal and practical. The README has an explicit warning: releases through v0.7.6 and source through the last-gpl-source branch are published under GPLv3. Later binary releases, including v0.8.1, are proprietary, and their source is not published. This means the repository you are looking at is a historical archive plus a distribution point for closed binaries. If you are evaluating this for an open source project, you can only use the GPLv3 code up to v0.7.6, and that version may lack the latest features. The repository also states it no longer accepts code contributions. So the open source aspect is frozen. For a user who wants the latest version, you are accepting proprietary terms, which is a different risk profile. The README points to a separate BINARY_LICENSE.md, but its contents are not included in the material, so you cannot evaluate those terms from this source alone.
Wrong tool cases: platform and workflow mismatches
Palmier Pro is the wrong tool if you are not on macOS 26 on Apple Silicon. The README is explicit: it requires macOS 26 (Tahoe) on Apple Silicon only. No Intel Macs, no Windows, no Linux. If your editing team uses a mix of platforms, this editor will not fit. It is also the wrong tool if you want an editor that works without an AI agent. The entire value proposition is the MCP integration and generative AI. If you need a traditional timeline editor with no agent involvement, there are many mature options. Another mismatch: if your workflow requires the editor to run in a server or CI environment, the MCP server only exists when the app is open on a desktop. There is no mention of a headless mode or a command-line interface. So agents cannot interact with a project unless a human has launched the app on a Mac.
Real alternatives and how they differ
The most direct alternative is Premiere Pro, which the README names as the north star. Premiere Pro is a mature, proprietary editor that runs on macOS and Windows, but it does not expose an MCP server. You would need to build your own integration, perhaps using scripting or plugins, to connect an AI agent. That is a fundamentally different approach: Palmier Pro bakes the agent connection into the app, while Premiere Pro requires external glue. Another alternative is DaVinci Resolve, which has a free version and a scripting API. Resolve's scripting API allows automation, but it is not MCP-native. You would need to write a bridge that translates MCP requests into Resolve's Python or Lua API. That gives you more control but also more work. The key difference is that Palmier Pro is designed for agent-first editing, while Resolve and Premiere are designed for human-first editing with optional automation. If you want zero-friction agent integration, Palmier Pro is unique. If you want a proven editor with broad platform support, the alternatives are safer.
Maintenance and upgrade costs
The maintenance picture is mixed. On one hand, the project is actively developed: the latest release v0.8.1 was pushed on 2026-08-28, and v0.7.6 and v0.7.5 came in the weeks before. So there is a steady release cadence. On the other hand, the repository no longer accepts code contributions, which means the open source community has no way to fix bugs or add features. If you rely on the GPLv3 source, you are on your own for patches. Upgrades are also gated by the license: moving from v0.7.6 to v0.8.1 means moving from GPLv3 to a proprietary license. You need to read the BINARY_LICENSE.md to understand the terms, but that file is not in the material. The README says the binary releases are proprietary, so you should assume the license restricts redistribution and modification. For a company that wants to embed or modify the editor, this is a hard blocker. For an individual user, the cost is the time to keep up with releases and the risk that a future version changes the license terms again.
Editorial conclusion
Adopt Palmier Pro if you are a macOS 26 Apple Silicon user who wants a video editor where AI agents can manipulate the timeline directly, and you are comfortable with the licensing split: source through v0.7.6 is GPLv3, but later binaries are proprietary. Do not adopt it if you need open source guarantees beyond v0.7.6 or if you require Windows or Intel Mac support. Before committing, verify that the MCP server at http://127.0.0.1:19789/mcp works with your specific agent (Claude Code, Codex, or Cursor) and confirm that the proprietary binary license terms match your workflow, since the repository no longer accepts code contributions.
Community notes