● Operate · AI assistants

MCP server
let Claude make videos in a workspace.

The MCP server lets an AI assistant such as Claude Desktop or Claude Code make videos in one workspace: "make a 20-second vertical video about our spring sale and render it". It talks to the studio through the REST API, so it runs on any computer that can reach your studio.

Model Context Protocol5 toolsNo dependencies

01Tools it offers

From src/mcp/server.ts; the tool list was checked with an MCP tools/list request against the built server.

Tool	What it does
`create_video_from_brief`	Starts a video from a description; the studio's AI writes the storyboard (costs credits)
`create_video_from_storyboard`	Creates a video from a full storyboard JSON (no AI call, no credits)
`render_video`	Queues a render of a ready video (costs credits)
`get_render`	Status of a render, and download links when it is done
`list_videos`	The workspace's videos with their status

02What you need

The API turned on and included in the workspace's plan, and an API key from the studio's Developers page (API and webhooks).
Node.js 22 or newer on the computer that runs the assistant.
The MCP server file. After npm run build it is dist/src/mcp/server.js in the Kinetica folder. It has no dependencies: copy that one file to another computer as kinetica-mcp.mjs and run it there (keep the .mjs ending).

Environment variable	Value
`STUDIO_URL`	The studio's address, e.g. `https://video.your-agency.com`
`STUDIO_API_KEY`	The workspace's key, `msk_…`

03Claude Desktop

Settings, Developer, Edit Config, and add to claude_desktop_config.json:

{
  "mcpServers": {
    "kinetica": {
      "command": "node",
      "args": ["/Users/you/kinetica-mcp.mjs"],
      "env": {
        "STUDIO_URL": "https://video.your-agency.com",
        "STUDIO_API_KEY": "msk_your_key_here"
      }
    }
  }
}

Restart Claude Desktop. The tools appear under the tools icon in a new chat.

04Claude Code

claude mcp add kinetica \
  -e STUDIO_URL=https://video.your-agency.com \
  -e STUDIO_API_KEY=msk_your_key_here \
  -- node /path/to/kinetica-mcp.mjs

Check it with claude mcp list.

05From the Kinetica folder

npm run -s mcp starts the same server (the compiled one in dist, else the TypeScript source). Always use -s: without it npm prints a line of its own on the output, which the assistant cannot read.

06Good to know

The assistant can only do what the key allows: one workspace, its credits, its plan's limits.
Tool errors come back as text the assistant reads, for example "The studio said (402): …". Nothing is retried by itself.
Until STUDIO_URL and STUDIO_API_KEY are both set, every tool answers with an explanation instead of acting.
Revoking the key on the Developers page stops the MCP server at once.

MCP serverlet Claude make videos in a workspace.