Run local video frame extraction through the CLI or MCP.

npx -y chrona-cli@0.1.0 --json doctor
npx -y chrona-cli@0.1.0 --json probe ./video.mp4
npx -y chrona-cli@0.1.0 --json extract ./video.mp4 --output frames.zip

• • The npm package installs pinned FFmpeg 6.1.1 and FFprobe binaries for supported systems.
• • Chrona uses a command option before an environment variable.
• • Set `CHRONA_FFMPEG` or `CHRONA_FFPROBE` to override an installed binary.
• • Next, Chrona uses the installed binary before a compatible binary on `PATH`.
• • If npm skips install scripts, Chrona uses compatible binaries on `PATH`.
• • If Chrona cannot run a binary, reinstall the package or pass an explicit path.
• • The binary packages include their GPL-3.0-or-later license files.
• • If you redistribute the binaries, read those license files.

Every browser outcome has a CLI command or option.

• Place `--json` before or after the command.
• A successful command writes one JSON value to standard output.
• A failed command writes one JSON error to standard output.
• Use `--progress json` for JSON Lines on standard error.
• Chrona never prompts in JSON mode.
• Paths in JSON results are absolute paths.

• • Plan schema version 2 stores retained source ranges, rate, crop, quality, and archive type.
• • Browser plans include source file size and duration.
• • Chrona rejects a plan after the source size or duration changes.
• • CLI plans can include local input and output paths.
• • Browser exports omit local paths.
• • Run `schema plan` to get the complete JSON Schema.

npx -y chrona-cli@0.1.0 --json plan ./video.mp4 --write edit.chrona.json
npx -y chrona-cli@0.1.0 --json extract ./video.mp4 --plan edit.chrona.json

Add this server to an MCP host. The host starts a pinned npx process.

{
  "mcpServers": {
    "chrona": {
      "command": "npx",
      "args": ["-y", "chrona-cli@0.1.0", "mcp"]
    }
  }
}