A
licenseNot graded
qualityC
maintenanceEnables AI video dubbing from any MCP-capable agent: upload a video or provide a URL, submit a dubbing job, poll progress, and download the finished MP4.
7
MIT
lipdub-mcp
Officialby marzvfx
Related Servers
Alternatives to lipdub-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceEnables AI agents to create lipsync videos, manage assets, and check generation status via the Sync API.2923 npm1MIT
vrmanofficial
AlicenseNot gradedqualityBmaintenanceEnables agents to generate 3D talking avatars from text descriptions or photos, and to render lip-synced talking videos from text using a photo, GLB avatar, or freshly assembled avatar. It also exposes tag vocabularies, asset search, and voice listings for building those avatars.MIT- AlicenseNot gradedqualityDmaintenanceEnables AI agents to edit videos through natural language, providing tools for timeline editing, audio management, rendering, and more.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to create, monitor, cancel, and download cinematic AI video renders through the Future Video Studio Agent API.25 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceEnables LLM agents to drive a self-hosted video toolkit through MCP tools, including lipsync, face restoration, ffmpeg operations, and metadata retrieval.1Do What The F*ck You Want To Public
TDQS
A4.7/5.0
Scored across 5 tools
Disambiguation5/5
Each tool has a clearly distinct role: connection check, listing, creating, one-shot status check, and blocking wait. The overlap between get_render and wait_for_render is explicitly disambiguated in their descriptions.
Naming Consistency5/5
All tools follow the same lipdub_ prefix with a consistent verb_noun pattern: check_connection, list_renders, create_render, get_render, wait_for_render. There are no naming style deviations.
Tool Count5/5
Five tools is well-scoped for this server's purpose. Each tool covers a necessary part of the render workflow without redundancy or bloat.
Completeness5/5
The tool surface covers the full render lifecycle: verify setup, create a render, wait for completion, retrieve the result, and list past renders. No obvious missing operation is needed for the stated domain.
Maintenance
ActivityMaintained
ResponsivenessNo issues