How to Use Muse Code with PilotCut MCP

The short version

Muse Code is Meta's terminal and CI coding agent on Muse Spark (default model muse-spark-1.2 in the docs). Connect it to PilotCut the same way you would any other MCP-capable coding agent: local MCP + CLI on a .pcbundle.

Muse Code is bring-your-own. It is not a PilotCut in-app catalog agent, and PilotCut does not ship Muse Code in the product agent picker. PilotCut's featured agents are Claude Code, ChatGPT Codex, Grok Build, GitHub Copilot, OpenCode, Antigravity.

Muse AI (the consumer personal agent on muse.ai) is a different product. This tutorial is Muse Code only.

What you need

• PilotCut on Mac (pilotcut.com). Free during beta
• Muse Code installed per Meta docs (macOS/Linux)
• A Meta / dev.meta.ai account that can complete Muse Code auth. Meta says expanded global access; verify eligibility at login
• For Muse billing dollars: Meta's live pricing and auth pages

Step 1: Install and auth Muse Code

curl -fsSL https://dev.meta.ai/install.sh | sh
muse --version
cd /path/to/your/edit-work
muse

Sign in with browser or API key. Use /login to reopen options. Headless later: META_API_KEY + muse exec (auth, extending).

Step 2: Open a local PilotCut project

1. Create or open a project. Footage lives in a local .pcbundle on the Mac.
2. Keep the editor window open. PilotCut exposes 83 purpose-built editing tools on the same surface as the UI and CLI (pilotcut tool list / describe / call).
3. Transport is local MCP for third-party clients. Point Muse Code at the open window's server.

Media and project stay on your Mac for edit, preview, and render. Prompts, transcript text, and frames an agent inspects follow that agent's provider.

Step 3: Declare PilotCut in Muse mcp_servers

In Muse Code settings, add an mcp_servers entry with transport stdio or streamable_http (MCP section). Use the connection details PilotCut shows for the open editor's local MCP server.

Step 4: Confirm protocol for silence and filler work

Named meaning-changing actions take confirm. For breath-safe silence and filler cleanup:

• edit-words actions cutSilences, removeWords, and removeDeadAir return a plan on confirm:false and apply on confirm:true.
• Breath-safe snap keeps dialogue intact when the plan is right.
• The Core Agent chat panel gates on riskTier. The agent CLI and third-party MCP clients (Muse Code included) are not gated. Muse Code can send both calls. Ask for the plan first if you want a human review in your loop.

Example prompt:

On this .pcbundle, propose cutSilences and removeDeadAir with confirm:false. Show the plan. Do not send confirm:true until I say so.

Step 5: Export and Final Cut handoff

Export full quality locally when the cut is ready. For Final Cut handoff, use the agent tool export type=fcpxml. It writes FCPXML 1.11 with absolute media paths, disk-capable from the agent CLI.

How it is built

PilotCut is AI-native: UI, CLI, and MCP clients share one tool registry and project model. Muse Code is just another coding agent with MCP, pointed at a local timeline, not at Muse AI consumer chores and not at computer-use on a finishing NLE.

The fastest editor for AI: 83 purpose-built tools, shaped by tens of thousands of hours of video-editing practice, so your agent and you waste less time and money.

Facts (checked 2026-09-15)

Also read

• Muse Code CLI headless exec with PilotCut
• How to use Claude Code / ChatGPT Codex with MCP/CLI for video editing
• Descript filler and silence cuts vs PilotCut propose-commit

Bottom line

Install Muse Code, authenticate, wire PilotCut's local MCP in mcp_servers, and run confirm:false plans on silence work before commit. Featured catalog agents stay Claude Code, ChatGPT Codex, Grok Build, GitHub Copilot, OpenCode, and Antigravity. Muse Code stays BYO.

Try PilotCut. Free during beta. Bring the agent you already pay for.