video-mcp
Related Servers
Alternatives to video-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server that turns video URLs into transcripts and important keyframes locally, with no cloud or API keys.356 npm5MIT
- AlicenseNot gradedqualityDmaintenanceA local MCP server for extracting YouTube video transcripts, metadata, and performing visual analysis using Gemini Vision or local Whisper models. It enables users to process video content through various tools for subtitle retrieval and frame analysis.10 npmMIT
- FlicenseNot gradedqualityDmaintenanceAn all-in-one MCP server for transcription, supporting YouTube, audio, and video with translation, summarization, chapter generation, subtitle export, and batch processing via 19 tools.-
- FlicenseNot gradedqualityCmaintenanceAn MCP server that automatically transcribes video content and burns stylized captions directly into the video file. It leverages the Groq Whisper API for fast transcription and supports multiple visual styles tailored for social media and professional content.-
- FlicenseNot gradedqualityDmaintenanceA local MCP server that gives Claude Desktop full video editing capabilities via FFmpeg, Whisper, and yt-dlp.-
- AlicenseNot gradedqualityDmaintenanceAn MCP server enabling video processing via natural language: transcription with Whisper, segment cutting with FFmpeg, and file management.MIT
TDQS
Scored across 9 tools
Most tools have distinct purposes, but video.create_preview and video.render are explicit aliases of the same operation, creating unnecessary ambiguity. The descriptions clarify the alias, which mitigates confusion, but the duplication is still a flaw.
Tool names follow a consistent pattern of domain prefix (video/subtitle/project) followed by an action verb (inspect, transcribe, clean, create_preview). The naming is uniform, though the presence of 'render' as an alias for 'create_preview' introduces slight redundancy without breaking the convention.
With 9 tools, the server is well-scoped for a video captioning workflow. Each tool (except the alias pair) serves a distinct step in the pipeline, and the count is within the ideal 3–15 range.
The tool set covers the core video-to-subtitle-to-export workflow: inspect, transcribe, caption, preview, clean, export SRT/ASS, and create an editable project. Minor gaps exist such as lack of an explicit transcript retrieval or deletion/update operations, but agents can work around these with the provided pipeline.