V MAX

Get started

one command

Running in about a minute.

The agent surface runs on your own machine and binds to localhost. Your footage never leaves it.

Start the server

Needs Node 18+, Python 3.12+, and ffmpeg on your PATH.

npx vmax-mcp --seed-demo

It prints a bearer token on start, and tells you on the first line whether the render back end is available — so you learn that at boot rather than at the end of a render.

Point Claude Desktop at it

Add this to claude_desktop_config.json, then restart Claude Desktop.

{
  "mcpServers": {
    "vmax": {
      "command": "npx",
      "args": ["-y", "vmax-mcp", "--seed-demo"]
    }
  }
}

Drive an edit

Ask Claude to read the timeline and propose a trim. What comes back is a diff and a version bump — never a surprise video. Retry the same request and you get replayed: true with the document unchanged, not a second edit.

The seeded fixture is a document with no media bound to it — enough to read, search, diff and edit, deliberately not enough to render. For a real render, create a project, upload an asset, and analyse it first.

Rendering needs one more step

The render engine binds a compiled component that cannot be published to the public Python registry, so npx alone can edit but not render. The server says so at boot and the job fails with the exact install command rather than hanging. Build instructions are in the package README.

Read the sourceHow it works

On security

The server binds to localhost by default and authenticates every request with a token generated at startup. Binding it to a public address is an explicit choice, and it refuses to start that way unless authentication is properly configured — because an open port with a development token printed to a terminal is worse than no server at all.