CueFrame

CueFrame — MCP, CLI and video API

CueFrame is a hosted service for composing, editing and rendering video. Connect your agent over MCP, automate an edit from the CLI, or integrate the REST API into your application. Each surface works with editable projects containing clips, captions and motion graphics, and renders them to MP4.

First render · Connection guide · Templates · API reference · Agent documentation index

*A frame from the Yosemite Peregrines template. Watch the video and try the same edit.*

MCP and agent plugin

For Claude Code, Codex, Cursor, VS Code, and other supported local agents, run this in your terminal with Node.js 24 or newer:

npx -y cueframe@0.12 install

The installer detects supported agents and adds the hosted CueFrame MCP endpoint to their configuration. It installs the skills in ~/.agents/skills and ~/.claude/skills, preserving locally modified skills by default. It can update multiple detected clients; use --dry-run to inspect the changes first.

Restart your agent session. Then ask:

Use CueFrame's get_account tool to check my connection and show my available credits.

Your client may prompt you to authenticate or open a browser. Sign in to CueFrame and authorize the connection; interactive OAuth clients need no API key. Cloud operations use credits. Check your balance and estimated costs before starting paid work; see cloud rates.

ChatGPT and Claude Desktop: use your client's hosted connector setup with https://api.cueframe.ai/v1/mcp, then authenticate. The terminal installer does not configure ChatGPT. See the connection guide and CueFrame connection skill for supported paths. Skills installation and hosted connector setup are separate steps.

Already connected? Skip installation and give your agent a video task. If CueFrame's tools do not appear, restart the client and check its MCP connection settings.

Make your first video

Try the Yosemite first-render walkthrough: render a template, change one word, and render again from the same project.

1. Download the full original footage from the National Park Service as yosemite-peregrines.mp4. Use the original source, because the finished demo has its title baked in. Follow the source's download and reuse guidance.
2. Give your connected agent the source file and this instruction:

Use CueFrame to start the yosemite-peregrines template from cueframe-ai/cueframe-templates with this original video. Load template.cueframe and its prepared subject matte. Preview the editable project and estimate cloud costs. After I approve the render, return the MP4 link and project ID.

1. After the first render, ask:

In that same project, replace the behind-subject title PHENOMENAL with EXTRAORDINARY. Preserve the footage, spoken captions, audio, timing, placement, and depth. Preview the changed title, estimate the render cost, and render after I approve.

The template selects 83.616–93.359 seconds of the original video. You should get two MP4s from one editable project. Uploading footage and running cloud operations use credits; the two renders are billed separately.

*The project stays editable: the desktop editor shows the title as a separate layer, alongside footage and captions. Watch the title change.*

What happens over MCP?

flowchart LR

A[Your request + footage] --> B[Your agent + CueFrame skills] B --> C[Hosted CueFrame MCP] C --> D[Editable project + preview] D --> E[Render job → MP4 link]

The agent inspects available tools, checks your account, prepares media and the project, previews changes, and submits a render. Long-running operations return IDs; the agent waits for completion and gives you the result. You do not need to write the tool calls yourself. The detailed quickstart explains the individual calls.

Starting a new video or adding to an existing edit? See when to start a template versus insert a component for discovery, media bindings, exact selection, preview and render.

For your next video, describe the result and provide the inputs:

Turn this interview into a 20-second vertical clip with word-timed captions. Preview the strongest moment and show estimated costs before rendering.

Find an image-carousel component for these product photos. Show suitable choices and their required inputs before creating the video.

Change only the final title in this project. Keep the rest of the edit unchanged.

Other installation options

Choose one setup path. A plugin installs the skills and hosted MCP configuration together. A server-only connection adds tools; skills provide the workflow guidance.

Claude Code and Codex plugins

Claude Code:

claude plugin marketplace add cueframe-ai/cueframe-mcp

claude plugin install cueframe@cueframe

Codex:

codex plugin marketplace add cueframe-ai/cueframe-mcp

codex plugin add cueframe@cueframe

Restart the session, authenticate when prompted, and ask the agent to call get_account.

Gemini CLI and Agent Skills clients

Gemini CLI:

gemini extensions install https://github.com/cueframe-ai/cueframe-mcp

Install skills in any client that supports Agent Skills:

npx skills add cueframe-ai/cueframe-mcp

Skills alone do not connect the MCP server. Add the hosted endpoint through your client's MCP settings if it is not already connected.

MCP server only, manual setup, and headless clients

The hosted endpoint is `https://api.cueframe.ai/v1/mcp`, using Streamable HTTP. For example, in Claude Code:

claude mcp add --transport http cueframe https://api.cueframe.ai/v1/mcp

For Cursor and VS Code, use the one-click links in the connection guide. Configuration keys differ between clients. Per-client examples are in examples/.

Interactive clients can use browser sign-in. Headless clients send Authorization: Bearer cf_live_…; see llms-install.md for authentication and stdio bridge options. The glama/ shim executes no tools and cannot be used to make videos.

Skills included

Skills teach the agent how to carry out video tasks. You describe the task; the agent selects the relevant guidance.

Claude Code's session hook and Cursor's rule help select the entry point. Other hosts load the installed skills through their own mechanisms. Scoped edits should preserve unrelated work.

CLI

Use the CLI for explicit video commands, shell scripts and structured JSON output. It connects to the hosted API; it does not run a local renderer. Requires Node.js 24 or newer.

npx -y cueframe@0.12 --help

npx -y cueframe@0.12 login npx -y cueframe@0.12 api GET /v1/me --json npx -y cueframe@0.12 describe --json

login opens the browser to authenticate. Headless scripts can supply CUEFRAME_API_KEY. The account request checks your connection and credits; describe lists command arguments and options without making an API call.

CLI guide · CLI walkthrough · Templates · npm package

API and TypeScript SDK

Use the REST API to create projects, import media, change compositions and follow render jobs from your application. Requests go to `https://api.cueframe.ai` with an API key from your account. Check your account before metered operations; cloud rendering and processing use credits.

For TypeScript or JavaScript on Node.js 24+, install the typed client:

npm install @cueframe/sdk

import { account, createClient } from "@cueframe/sdk";

if (!process.env.CUEFRAME_API_KEY) throw new Error("Set CUEFRAME_API_KEY"); createClient({ baseUrl: "https://api.cueframe.ai", apiKey: process.env.CUEFRAME_API_KEY, }); const result = await account.getAccount(); console.log(result.plan, result.entitlements);

Other languages can call REST directly or generate a client from the versioned public OpenAPI contract. The SDK is a client for the hosted service, not the server implementation.

API walkthrough · API reference · SDK guide · Render example · npm package

What this repository contains

This repository contains the agent plugin, developer toolkit, and registry files. The hosted MCP server is maintained separately in the application repository. You connect to CueFrame's hosted service; cloning this repository does not run that service locally.

| skills/, host manifests, hooks/, [`rules/