Skip to content

Agents

Connect an agent

Add the Vukem Video MCP server to Claude Code, Cursor or another MCP client, or drive the CLI from a shell.

Last updated:

Claude Code#

Terminal
claude mcp add vukem-video -- vukem-video mcp

The server speaks MCP over standard input and output. When no other process owns your workspace, vukem-video mcp becomes its owner for as long as it runs; when the editor server is already running, it talks to that server instead, so the agent and the browser see the same project.

Other MCP clients#

Any client that starts a stdio server takes the same command. In a JSON configuration file it looks like this:

JSON
{
  "mcpServers": {
    "vukem-video": { "command": "vukem-video", "args": ["mcp"] }
  }
}

The server names the actor of each edit after the client, as local:<client name>, so the history shows who did what.

A remote server#

Set VUKEM_VIDEO_URL and VUKEM_VIDEO_KEY and the CLI and the stdio server talk to that server with the API key. See the configuration variables.

The CLI#

An agent with a shell can use the CLI instead. Add --json for one JSON document per command and --actor <label> to name itself:

Terminal
vukem-video project:create --name "Launch teaser" --json --actor claude-code
vukem-video media:import clip.mov --project prj_7k2m9x4q1b --json
vukem-video export --project prj_7k2m9x4q1b --json

Exit code 0 is success, 2 is a retryable error or a --wait that timed out, and 1 is any other failure. Every command is in the CLI reference.