Gemini-Video-MCP
Related Servers
Alternatives to Gemini-Video-MCP
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceEnables local media processing (video/audio) using FFmpeg and FFprobe, allowing frame extraction, audio conversion, and metadata retrieval through natural language.5-
- AlicenseAqualityAmaintenanceEnables AI clients to watch local video files or YouTube/Bilibili and other supported URLs, receiving timestamped transcripts, subtitles, searchable text and keyframe contact sheets. Runs fully offline with local speech recognition and bundled ffmpeg, so no API key or cloud upload is needed.673 PyPI9MIT
- AlicenseBqualityDmaintenanceEnables conversational analysis of YouTube videos using Gemini 2.5 Pro, supporting multi-turn sessions, direct URL processing, and local video uploads.101MIT
- FlicenseNot gradedqualityDmaintenanceBridges Claude and video content by extracting keyframes and transcribing audio, enabling Claude to analyze video files.-
- FlicenseAqualityDmaintenanceExtracts timestamped screenshots from local videos, enabling Claude to produce visual walkthroughs without audio analysis or cloud processing.4-
- AlicenseAqualityBmaintenanceProvides image and video analysis capabilities for LLMs, with local preprocessing (ffmpeg/OpenCV) and any OpenAI-compatible vision model for understanding and Q&A.4MIT
TDQS
Scored across 5 tools
Each tool serves a clearly distinct purpose: cost estimation, local video description, URL-based description, frame viewing, and upload retrieval. The two description tools are cleanly separated by input source (local path vs URL) with explicit parameter names, eliminating ambiguity.
All tools follow a consistent verb_noun snake_case pattern (e.g., estimate_cost, describe_video, view_media, get_upload_url). The describe_video_url variant appropriately uses a suffix to indicate its remote input mode, preserving overall consistency.
With five tools, the server is well-scoped for video understanding workflows. Each tool covers a distinct step in the process—cost planning, local/remote description, visual extraction, and file upload—without redundant or missing functionality.
The tool surface fully covers the expected video analysis lifecycle: estimating token usage, uploading or referencing videos, describing content from local/URL sources, and examining frames. No essential operation is missing, and unsupported platform limitations are explicitly documented as out of scope.