video-research-mcp

Ask questions across recordings and documents, then inspect the source frames, transcripts and clips behind the answer. The server exposes 120 MCP tools for video, audio and image operations, document analysis, web and academic research, and saved knowledge. Agent workflows connect those tools into a research or production task.

Use it in Codex, Claude Code, or any client that supports stdio Model Context Protocol. Gemini handles the main analysis and research routes; local tools inspect and transform source files. Optional providers and runtimes extend that core.

Release target · npm target · PyPI target · Source target

This guide targets the 0.8.0-rc.2 candidate (Python 0.8.0rc2). Installation examples pin this candidate; reference links use its source tag. Stable 0.7.1 predates the native Codex plugin and the expanded media surface.

From source material to a useful result

For example, ask your client:

Compare ~/recordings/design-review.mp4 with ~/docs/requirements.pdf.
Identify decisions that change a requirement. Cite recording timestamps and
relevant document pages, distinguish explicit decisions from interpretation,
and flag anything the sources do not establish.

Workflows combine tools; individual MCP calls return their own results. Source hashes identify bytes, and export manifests retain how an artifact was produced. Model timestamps, citations and interpretations still need checking against the original material. Sampling a recording does not establish complete coverage.

Install

You need Python 3.11+, uv with uvx on your client's PATH, and a Gemini API key for Gemini requests. Plugin installation also needs Node.js 22+ and npm. Install FFmpeg/FFprobe for local media inspection, frame extraction and clip exports. Other operations may need an optional dependency or configured backend.

By default, the server reads process environment variables first, then ~/.config/video-research-mcp/.env, then defaults. Project installations can select a separate credential file. Add your key to the shared file for the routes below, keeping any existing settings:

GEMINI_API_KEY=your-gemini-api-key

Keep the file private (chmod 600 ~/.config/video-research-mcp/.env). Codex plugin servers receive a filtered environment, so this file is the reliable credential route there. Provider analysis sends source material to the configured service and can incur usage charges. A selected analysis interval does not necessarily limit the uploaded file.

Codex: native plugin

The plugin supplies 24 skills and the version-pinned research server. The native npm installation check covered RC1 (0.8.0-rc.1) on Codex 0.160.0. That historical check does not establish RC2 acceptance on Codex 0.160.1. You do not run the Claude installer for this route.

For a new installation, save this catalog as ~/.local/share/video-research-mcp/.agents/plugins/marketplace.json, creating its parent directories if needed:

{
  "name": "video-research",
  "interface": { "displayName": "Video Research" },
  "plugins": [
    {
      "name": "video-research",
      "source": {
        "source": "npm",
        "package": "video-research-mcp",
        "version": "0.8.0-rc.2"
      },
      "policy": { "installation": "AVAILABLE", "authentication": "ON_INSTALL" },
      "category": "Productivity"
    }
  ]
}

codex plugin marketplace add ~/.local/share/video-research-mcp
codex plugin add video-research@video-research
codex plugin list --json

Start a fresh Codex session. Check that video-research@video-research is enabled, its source is npm at 0.8.0-rc.2, and the server's tools are available.

For an existing installation, use the native plugin and migration guide. Back up local plugin edits before reinstalling: Codex replaces its managed cache. A manual mcp_servers.video-research entry can hide the plugin server. In the historical RC1 check on Codex 0.160.0, this also occurred when the entry was disabled; the guide describes the specific configuration to remove.

Claude Code: workflow installer

npx video-research-mcp@0.8.0-rc.2 --global

This installs slash commands, skills and agents into ~/.claude/, registers the research server in ~/.claude.json, and creates a credential template if needed. Set the key, restart Claude Code and inspect /mcp. Use /gr:advisor to select a workflow, or /gr:video, /gr:research and /gr:analyze to start directly.

Use --local for project scope and set the key in ./.config/video-research-mcp/.env; this replaces the shared credential-file route. Use --global --check to inspect the global installation. Updates preserve modified workflow files and custom configuration. See installer options and recovery for scope, checkpoints and rollback.

Other MCP clients: server only

Use your client's stdio registration format. A typical JSON entry is:

{
  "mcpServers": {
    "video-research": {
      "command": "uvx",
      "args": ["video-research-mcp==0.8.0-rc.2"]
    }
  }
}

This connects the same tools; agent workflows are installed separately. Python package filenames use the normalized spelling 0.8.0rc2.

Verify your first connection

Ask the client to call infra_configure with no arguments. It returns the running configuration without making an analysis request. Then try a tool on material you can inspect yourself. A successful connection verifies setup; checking the returned evidence verifies the particular result.

Configure only what the task needs

Research works without Weaviate. When storage is configured, write-through errors are non-fatal; verify the stored record when persistence matters. The knowledge-store guide covers embeddings, collections and optional query dependencies. For a manually configured server, retain the version pin when adding extras, for example uvx 'video-research-mcp[tracing,agents]==0.8.0-rc.2'. The full runtime configuration lives in ServerConfig.

Image edits, OCR, speech inference, Blender, FreeCAD and local model services have additional runtime or backend requirements. Installing the plugin does not install those runtimes, model weights or provider accounts. Inspect the relevant skill and its prerequisites before using an optional integration.

For video production, the separate explainer companion orchestrates an external rendering pipeline; the scene-agent companion handles scene-code generation. Neither is required for research. Production skills also provide workflows for narration, image generation, clip generation and assembly.

Inspect and extend

• Tool implementations: exact parameters and behavior. Your client's discovered MCP schemas describe the running version.
• Windowed video analysis: dry-run budgets, continuation, upload limits and retained partial results.
• Contributing: source setup and checks.
• Security policy: local access, provider boundaries and reporting.
• Changelog: changes in this candidate.

For RC1 (0.8.0-rc.1) on Codex 0.160.0, packaged installation, native tool discovery, local tool journeys and fresh-session restart were verified. Current RC2 archive and installer checks establish source and archive consistency only; native acceptance on Codex 0.160.1 requires a check of the current candidate. The 120 tool contracts do not establish qualification of every optional runtime. Live-provider quality and complete end-to-end comparative acceptance remain open.

Created by Fausto Albers · Wonder Why. Built with Google Gemini, FastMCP and Pydantic, with optional knowledge and tracing integrations. Project code is MIT licensed; third-party notices cover bundled components with their own terms.