mcp-video-vision
Related Servers
Alternatives to mcp-video-vision
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceAn MCP server enabling Claude Code to analyze any video (local file, URL, or Jira ticket attachment) by extracting frame images and audio transcripts, or using Gemini for native video analysis.4MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server for comprehensive video analysis — AI-powered transcription, visual frame analysis, and metadata extraction from 1000+ platforms.1MIT

video-analyzerofficial
FlicenseNot gradedqualityDmaintenanceMCP server enabling video analysis via scene detection, audio transcription, visual description, and stylistic fingerprinting, with tools for full pipeline execution and storyboard generation.-- FlicenseNot gradedqualityCmaintenanceMCP server exposing claude-video functionality for claude.ai web UI via HTTP+SSE, enabling video watching and analysis from claude.ai.-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that uses Google's Gemini API to analyze videos and convert them to text descriptions that Claude Code can understand and act upon.33 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables LLMs to analyze video content by extracting frames as base64 images and retrieving video metadata using ffmpeg.9 npmMIT
TDQS
Scored across 8 tools
Most tools have clearly distinct purposes (e.g., transcribe, video_info, generate_xml). However, there is some overlap: decupar and detect_scenes both detect scenes, and catalog_brolls also extracts representative frames, which could cause confusion. The descriptions help differentiate but ambiguity remains for these tools.
Tool names mix English and Portuguese (catalog_brolls, decurpar vs. detect_scenes, extract_frames). Naming patterns are inconsistent: some are verb_noun (detect_scenes, extract_frames), others are noun_verb? (catalog_brolls) or single verbs (decupar). This inconsistency makes it harder to predict tool functions from names alone.
8 tools is an appropriate number for a video analysis and editing server. Each tool covers a distinct part of the workflow (metadata, scene detection, frame extraction, transcription, XML generation) without being overwhelming or too sparse.
The tool set covers the core video analysis pipeline: metadata extraction, scene detection, frame extraction, audio transcription, and XML export for editing. Minor gaps exist: no tool for searching within transcriptions or for directly combining scenes into edit decisions, but these are manageable for an agent.