vidlens-mcp
Related Servers
Alternatives to vidlens-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables local video inspection and offline transcription with timestamped JSON and Markdown output, enforced filesystem boundaries, and reproducible content-addressed caching.2MIT
- AlicenseAqualityBmaintenanceEnables AI agents to analyze videos by producing timestamped transcripts, keyframe contact sheets, and metadata reports from local files or online URLs, fully offline and without API keys.6MIT
- AlicenseNot gradedqualityDmaintenanceDownloads and analyzes videos from platforms like Instagram, YouTube, and TikTok locally, returning keyframes and optional transcripts.MIT
- 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.696 PyPI12MIT
- AlicenseNot gradedqualityAmaintenanceProvides local, offline transcription, keyframe extraction, OCR, and pre-publish review of audio, video, and image files, enabling AI agents to see and hear media without cloud or API keys.30 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to download, convert, and visually analyze videos by providing timestamped frames and locally transcribed speech, all without API keys.MIT
TDQS
Scored across 18 tools
Descriptions actively steer the agent away from the wrong tool (e.g. video_subs before ASR, video_sheet/frames instead of video_full, video_window for a single span vs video_watch for incremental progress), which is unusually strong guidance. Still, there are clusters of near-neighbours: video_brief / video_watch / video_window all can yield transcripts of the same footage, and video_sheet / video_frames / video_visual_scan / video_ocr all sample frames, so a hurried agent could easily pick the wrong one.
Nearly everything follows a single `video_<noun>` scheme with short, readable suffixes. The two infrastructure tools break the prefix (vidlens_models, vidlens_doctor), and a few names mix styles (video_job_start is noun_verb, video_full is an adjective), but the overall set is predictable.
18 tools is on the heavy side, but they form a deliberate cost tier (meta → plan → window → sheet → OCR → job) rather than a flat pile. Each tool has a stated cheaper alternative it exists to replace, though a few of the visual/transcript tools could plausibly be merged.
The surface covers the full video-analysis lifecycle: metadata, subtitles, planning, incremental watching, time windows, audio events, soundscape, frame/sheet/scan visuals, OCR, comments, plus model management, diagnostics and async job polling for long runs. No obvious dead ends remain for the stated domain.