encoding-devops
Related Servers
Alternatives to encoding-devops
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceMCP server that enables video analysis capabilities to Claude, including frame extraction, scene detection, and video metadata retrieval.8-
- AlicenseBqualityCmaintenanceAn MCP server that integrates Shaka Packager with Claude AI applications, enabling Claude to analyze, transcode, and package video files for streaming in formats like HLS and DASH.44MIT
- FlicenseNot gradedqualityBmaintenanceMCP server for managing video pipelines, integrating media processing (TTS, STT, image generation) and video editing, with a structured plugin system and tunnel to Claude AI Web.-
- FlicenseNot gradedqualityDmaintenanceAn MCP server that gives Claude Code text-to-speech capabilities with support for multiple simultaneous instances, message queuing, and a web UI for monitoring.1-
- AlicenseAqualityDmaintenanceAn MCP server that turns Claude into a full image production studio, enabling creation, editing, resizing, and brand-consistent asset generation across multiple platforms.6MIT
- AlicenseAqualityBmaintenanceMCP server for CodeRocket Deploy providing AI-generated CI/CD workflows and AI code review as tools inside Claude Code.94 npmMIT
TDQS
Scored across 8 tools
Most tools target clear, distinct resources (clients, cluster status, movie search, email). The three job-related tools (get_job_by_name, get_job_tasks_by_id, get_latest_jobs) share a resource but differ in intent, so only minor confusion is possible.
Names follow a consistent snake_case verb_noun pattern (get_job_by_name, get_movie_details, search_movie). The is_cluster_busy predicate is a reasonable deviation for a boolean check rather than a true inconsistency.
Eight tools is well-scoped for this domain, with each covering a distinct query. No redundant or filler tools pad the surface.
The surface is read-only: it exposes job lookups, cluster status, and movie info but no submit/create/cancel/retry job operations, which are core to an encoding-ops workflow. Client and email handling are present but job lifecycle coverage is one-sided.