I’d rather drive
Saved truck footage, timed shots and edit notes in one board, ready to refer to while writing the next brief.

MCP connector Live
MCP connects an application to tools or context.
YouTube capabilities depend on the server you use.
Connect your Library · up to 92 tools · 90 never spend credits

If you want a saved reference, name the film and ask for the source of the answer.
For example: “Find the Subaru Outback study and describe its opening from the saved report. Do not start a new analysis.” Then inspect the report link and source attribution.
Reading an existing study and starting a new analysis are separate actions. A new analysis uses the applicable allowance or credits. Check the product for the options available to your account.
The protocol alone does not promise that a model can watch a video, retrieve every transcript, or hear every sound. MCP architecture · Checked November 3, 2026.
One connector URL and one sign-in. Pick your app.
One address for every Claude surface.
https://mcp.videngineer.com/mcp
Sign in to your own videngineer account and approve access. The tools appear in your chat.
Run this in your terminal.
claude mcp add --transport http videngineer https://mcp.videngineer.com/mcp
In Claude Code, run /mcp, pick videngineer and sign in. Approve access to your own account and the tools are ready.
Prefer to run it on your own machine? Use the local connector with an API key.
Codex, Grok and the rest have their own guides below.
Connecting is free. Plans start at $39/mo for 60 minutes of video a month. See plans
Connect the agent you already pay for. It organises your own footage, turns the parts that work into reusable formats and saves them to your Library, with the library of winning videos behind it.
Add the connector in Claude, Claude Code, Codex or Grok and sign in. How to add it
Drop your clips into your Library in videngineer. Agents that run on your computer, like Claude Code and Codex, can upload a folder for you.
Ask your agent to storyboard the footage on the Agentic Canvas next to a winning video: what each clip shows, the best moments and the order to cut them in.
“Open my teardown of the launch video I saved and map the clips in my Library folder Farm shoot on a new board in the same structure: what’s in each clip, the best three seconds, and the order you’d cut it in.”
“Save the opening of this board as a template so I can use it for the next shoot.”
Your agent looks at your footage itself, as still frames. Agents on your computer take the stills from your files. In a chat, attach a few stills from each clip.
No credits: uploading, boards, cards, notes and templates never use minutes or credits. Your plan still sets: file space (250 GB on Pro, 1 TB on Power, 2 TB on Studio), files up to 2 GB and 30 minutes each, up to 500 cards on a board, and a monthly allowance of connector requests. A new analysis or a cut blueprint uses your plan, and only when you ask for one.
Same account, same tools. Pick yours for the exact steps.
Reading never spends credits. Two tools can, and only when you ask.
read-only · 0 credits — 39
spends credits · only when you ask — 2
builds & board edits · 0 credits from your balance — 51
Tool availability depends on your plan, permissions and enabled features. Changes require your request; permanent deletion requires confirmation.
Private uploads use your footage storage: 250 GB on Pro, 1 TB on Power, 2 TB on Studio, 5 GB during a trial. Videos up to 2 GB and 30 min each, images and audio up to 50 MB. Uploads are stored, not analysed.
MCP (Model Context Protocol) is the standard way AI agents plug into the apps you use. With the videngineer connector, your agent reads your teardowns and Library, searches the public teardown library, starts a teardown from a link and lays out a Canvas board. Canvas needs a paid plan.
Yes. Connecting is free, and reading results you already have never spends credits. Starting a teardown uses your plan’s allowance. See plans.
Your agent signs in with your own videngineer account, so there’s no API key in the chat. You approve the access it gets, and you can disconnect at any time in your account.
Claude on the web and desktop, Claude Code, Codex, and Grok as a custom connector, today. The ChatGPT app and the Muse connector are in review. Perplexity, Cursor, OpenClaw and Hermes are coming. Each agent has its own guide above.
What it gives you, our own boards, how it fits and the local setup.
Your references and decisions stay in videngineer. The connector lets you work with them from another app.
Search your teardowns by topic, hook or format, and your cuts by subject or camera move. Open a saved Library folder to find the references you kept.

Read the script, cuts and sound from a teardown. Search the notes on a Canvas board and open the full note behind a decision.

On a paid plan, ask for notes, labels, arrows and saved references to be arranged on Canvas. Open that same board in videngineer to review and change the plan.

These are our own film plans, opened through the local connector. The connector returns the saved work for you to study and plan from.
Saved truck footage, timed shots and edit notes in one board, ready to refer to while writing the next brief.

The character sheet and shot-by-shot plan stay together, so the next decision can start from the choices already made.

The connector brings your saved study into the app where you are working. Canvas holds the plan you hand off.
Sign in to connect, or use your personal API key locally. Reading existing results does not spend analysis credits; starting a teardown uses your plan’s allowance, and requesting a cut blueprint can spend credits.
Manage your connection or revoke your local key in your account.
Local setup is documented for Claude Desktop and Claude Code. Other apps are not tested yet; use one of the guides above.
Open Account → API access → Generate key. Your account shows whether key access is available.
Open API access →Install Python and the connector runtime, then save the connector file on your machine.
Download the connector →Set the local file path and your key in the config below. Restart your app, then ask about a teardown or board.
Download example config →pip install "mcp[cli]" curl -O https://videngineer.com/mcp/videngineer_mcp.py
Claude Desktop: use claude_desktop_config.json. Claude Code: use .mcp.json in your project. Replace the example path and key with your own.
{
"mcpServers": {
"videngineer": {
"command": "python",
"args": ["/absolute/path/to/videngineer_mcp.py"],
"env": { "VIDENGINEER_API_KEY": "your-key" }
}
}
}
Restart your app. Try: “Find the hooks in my recent teardowns.” On a paid plan, try: “Open my Canvas board and read the shot notes.”
Read your teardown reports, scripts, cuts, scenes, saved assets, Sound Kit and cast details. Compare several saved analyses, open Library folders, browse public teardowns and their tags, and search Canvas notes and references, and inspect version history.
Start a teardown from a supported video link, check its progress, or request a cut blueprint. On a paid plan, build a missing cut grid without using wallet credits.
On a paid plan, create boards and folders, add saved references or a public media URL to your Library, and arrange cards, notes and arrows. Save a new board version, restore an earlier version, or move a board to Recently Deleted, where it stays restorable in the app.
Start with a free 20-min call with Mark.
Book a free 20-min call