videoctx

io.github.dunfredPublished by GitHub account dunfredv0.1.5Updated Oct 30, 2026

Read videos like images: index once locally, query the text layer, fetch frames on demand.

Overview

AI-generated overview

Locally indexes video files into a text-plus-frames index so an assistant can read, search and visually inspect videos without re-ingesting them.

What you can do
  • Index a video file locally into shots, keyframes and a speech transcript
  • Read a cheap text layer of shots, captions and transcript, or a thumbnail sweep of one frame per shot
  • Fetch evenly spaced frames from a chosen time range, optionally at higher resolution
  • Search the transcript by keyword and find moments by natural-language visual description
  • Use returned timestamps to zoom into the right range with frame fetches
When to use it
Useful when you want an assistant to answer questions about lectures, meetings, interviews, screen recordings or a video archive, and prefer one local indexing pass over re-sending whole videos to a model on every question.
Requirements
Runs as a local stdio process installed from PyPI with uvx. Needs Python and ffmpeg on PATH. Core tools and indexing run fully locally with no API key; semantic visual search needs embeddings built once per index with the videoctx embed command. The separate command-line question-answering feature uses an Anthropic API key, but the MCP server itself makes no model calls.
Before you install
Indexing writes a .vctx directory next to the video and takes roughly 10-20% of the video's duration, so large archives take time and disk. Frames are token-expensive, especially at high detail. Optional visual captions can be generated by a third-party VLM, which sends video frames off the machine. The README's cost figures assume paid model usage for question answering.

Installation

In SourceWeft

  1. Open videoctx in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

videoctx

Index a video once. Query it cheaply, forever, with any LLM.

videoctx ("video context") turns any video into an open, portable Video Context index (.vctx, see SPEC.md) using only local, model-free tools: ffmpeg keyframes, PySceneDetect shot boundaries, faster-whisper transcripts, and optional one-line visual captions from any cheap VLM. An agent answers most questions from the index's text layer for fractions of a cent, and pulls individual frames on demand only when a question needs pixels.

videoctx index lecture.mp4          # one-time, local, freevideoctx show  lecture.vctx         # the text view the model readsvideoctx ask   lecture.vctx "What diagram is shown when she explains backprop?"

What people use it for

Ask questions about videos the way you'd ask about a document:

  • Lectures and courses: "Summarize this 50-minute lecture." "Where does she explain backpropagation, and what's on the slide at that moment?"
  • Meetings and interviews: "List the action items with timestamps." "Find the moment the client pushed back on pricing."
  • Screen recordings: "At what time does the error appear, and what does the dialog say?"
  • Content creation: "Find the three strongest moments for short clips." "Generate chapter markers."
  • Video archives: index a folder of talks once, then every future question across all of them costs pennies and answers in seconds.
  • AI agents: give any MCP-capable agent (Claude Code, Cursor, ...) the ability to read video at all.

Who this is for: developers and anyone comfortable running a few terminal commands. You'll need Python, ffmpeg, and an Anthropic API key for question-answering (indexing itself is free and offline). If that's not you yet, star/watch the repo: a no-install version is on the roadmap.

Why

Native video ingestion re-tokenizes the whole video on every question: an hour of footage is ~250-350k tokens, every single time. Proprietary video platforms index into closed representations behind per-minute pricing. videoctx is the third option: an open on-disk format any model can consume, produced by free tools, where the marginal cost of a follow-up question on an hour-long video is about $0.02.

Benchmark results (Video-MME, Oct 2026)

Full protocol and honest cost accounting (including prompt-cache write premiums) in paper/draft.md. Query model: Claude Opus 4.8.

Numbers below are single-touch runs of the frozen configs (v0.2: captions + OCR + evidence rules, Opus 4.8 loop; v0.3, 2026-10-21: adds text-evidence rules, verbatim transcript quotes and a final letter-vs-evidence check) under full cost accounting. Where we measured the same configuration more than once, we report the observed range: on n=150, single runs wobble by 2-3 questions; on n=30, by 2-3 questions (= 7-10 points). Treat sub-3-point deltas on this benchmark as noise.

Subset composition caveat: videos were taken in Video-MME dataset order, which clusters by domain. The medium and long cells are entirely Knowledge-domain videos; the short cells are 76-88% Knowledge (remainder Film & Television). Read these as Knowledge-dominated subsets of Video-MME, not the full benchmark; future splits will be domain-stratified.

Short videos, held-out test half (n=150):

MethodAccuracy$/question
videoctx v0.484.7%$0.025
videoctx v0.382.0%$0.025
videoctx v0.280.7% (equivalent configs ranged 80.7-85.3%)$0.025
Uniform frame sampling74.0%$0.0172
Gemini Flash-Lite native (pilot 30)70.0%$0.0009
Gemini Flash native (pilot 30)53.3%$0.0047

Medium videos, 4-15 min (n=30, wide error bars):

MethodAccuracy$/question
Uniform frame sampling80.0%$0.081
videoctx v0.7 (contact sheet 60@512 in cached prefix)70.0%$0.092 first-touch, ~$0.02 follow-up
videoctx v0.2 through v0.666.7% (near-identical failure set)$0.051-0.062
Gemini Flash-Lite native70.0%$0.0034

Medium is our weakest cell and remains the named target: naive leads on raw accuracy. Ten questions failed identically across five configs (prompt rules, a text-view bug fix, dense captions, a 24-thumb contact sheet); the sixth config, a 60-thumbnail 512px contact sheet baked into the cached prefix, recovered one. The receipts tell a consistent story: these videos are fast-cut and fully captioned, and the remaining gap is visual detail bandwidth at question time, naive's one structural advantage. We publish the ladder rather than only its best rung.

Correction (2026-10-21): a text-view bug had been dropping the header line (duration, shot count) on every OCR-enriched index since OCR shipped; all v0.2/v0.3 numbers were measured under that bug. v0.4 is the corrected configuration (short +2.7 points, long back to 80.0%, medium unchanged).

Long videos, 30-60 minutes (n=30):

MethodAccuracy$/questionFollow-up $/question
videoctx v0.5 (dense captions)83.3%$0.109 cold (measured $0.047, see note)$0.021
videoctx v0.480.0%$0.099$0.019
videoctx v0.2 / v0.380.0% / 76.7% (n=30 noise band)$0.098$0.019

Cost correction (2026-10-22): the v0.5 long run started 57 minutes after the v0.4 run, and for the 7 of 10 videos whose text views were unchanged by dense captioning, it silently inherited v0.4's still-live 1-hour prompt caches, flattering first-question costs. $0.109/q is the cold-equivalent (first question $0.285, follow-ups $0.021 as measured). Benchmark runs are now cache-salted per config so this cannot recur. | Uniform frame sampling (60-frame cap) | 70.0% | $0.133 | $0.133 | | Gemini Flash-Lite native | 76.7% | $0.022 | $0.022 (5-9 min latency/q) | | Native ingestion (published Pro rates, est.) | pending | ~$0.50 | ~$0.50 |

One-time index cost: ~$0.10-0.25 per hour of video (captions + local OCR + local embeddings), pennies otherwise.

Cost correction history: early short-video figures ($0.0067/q) undercounted prompt-cache write premiums; the metering was fixed 2026-10-18 and all figures above are fully loaded. Details in the paper's Section 7.3.

Install

git clone <repo> && cd videoctxuv venv && uv pip install -e .

Requires ffmpeg on PATH. videoctx index and the MCP server's core tools run fully locally with no API key. videoctx ask uses the Anthropic API (ANTHROPIC_API_KEY or an ant auth login profile).

MCP server: let any agent read videos

claude mcp add videoctx -- $(pwd)/.venv/bin/videoctx-mcp

The calling agent's own model reads the text layer and frames directly; the server makes no model calls and needs no key. Tools: video_overview (cheap text layer), survey_video (one thumbnail per shot), get_frames(path, t0, t1, detail), transcript_search, find_moments (semantic visual search, needs videoctx embed once per index), index_video. The server's instructions carry the evidence rule: visual answers must cite fetched frames, never general knowledge.

Reproduce the benchmark

uv pip install -e ".[eval]"python eval/prepare_videomme.py --duration short --videos 100 --out eval/datapython eval/split_dev_test.py eval/data/videomme_short.jsonlpython eval/run.py eval/data/videomme_short_test.jsonl --methods videoctx,naive

eval/methods.py documents each baseline. Cost accounting counts cache writes at their real premium (1.25x / 2x by TTL); see the paper's Section 7.3 for the accounting traps this avoids.

Format

The .vctx directory is plain JSON + JPEG: manifest.json (provenance, parameters, source hash), index.json (shots, keyframes, transcript, captions), frames/. Consumers must ignore unknown keys; enrichment layers (OCR, embeddings) are reserved in SPEC.md v0.1.

Status and roadmap

Working and benchmarked: indexing, query loop, MCP server, eval harness. Next: medium-duration subset, Pro-tier native baseline, cross-model portability runs (same indexes via non-Claude models), OCR and per-shot embedding layers, spec v1.0.

License

Apache-2.0. Copyright 2026 Fred Dunyo.

Source: README.md at commit 72fac17

Tools

6

index_video

Index a video file for querying (shots, keyframes, speech transcript). Runs locally; takes roughly 10-20% of the video's duration. Idempotent - returns immediately if the video is already indexed. The other tools auto-index too, so calling this first is only needed to control when the wait happens.

Parameterspathrequired

video_overview

The cheap text layer of a video: shot list with timestamps and visual captions (when present), interleaved with the speech transcript. Read this before fetching any frames: it answers most questions by itself.

Parameterspathrequired

survey_video

One small thumbnail per shot across the whole video (subsampled to at most 24), each labeled with its timestamp. Cheap visual sweep for locating the relevant moment before zooming in with get_frames.

Parameterspathrequired

get_frames

Frames evenly spaced across [start_s, end_s]. Frames are expensive: use the narrowest range the question allows, and raise max_frames (up to 8) only when a sparse sample missed the moment. Set detail='high' (2x resolution, ~4x token cost) when small text, colors, patterns, or fine object details matter.

Parameterspathrequiredend_srequireddetailstart_srequiredmax_frames

find_moments

Semantic visual search: find the moments that best match a natural language description (e.g. 'a red car at night'), using local CLIP embeddings. Returns the top matches as timestamped thumbnails: use the timestamps to zoom in with get_frames. Requires embeddings built once with `videoctx embed <index>`; cheaper and more targeted than survey_video when you know what you are looking for.

Parameterspathrequiredtop_kdescriptionrequired

Version history

3
  1. v0.1.5LatestOct 22, 2026
  2. v0.1.4Oct 21, 2026
  3. v0.1.2Oct 18, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts