Sync MCP Server
OfficialRelated Servers
Alternatives to Sync MCP Server
No user-submitted related servers found.
Related Servers
AlicenseAqualityAmaintenanceEnables AI agents to lip-sync video to a different audio track via LipDub 2, including creating renders, checking statuses, and retrieving results.524 npmMIT- AlicenseNot gradedqualityDmaintenanceEnables AI video generation from text prompts, status monitoring, and video management through the Sisif AI Video API.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to generate images, videos, and lip-sync media, and to query wallet balances via the Open Generative Studio instance.MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to generate AI avatar videos, manage templates, and work with assets through natural language commands via the HeyGen API.7MIT

CraftStory MCP Serverofficial
AlicenseAqualityAmaintenanceEnables MCP clients to create talking-avatar videos of any length from a photo plus audio, and short AI clips with generated sound or lip-sync, through the CraftStory API. It also covers voice and avatar listing, speech generation, cost previews, job status and result retrieval, and upscaling.1149 npmMIT
@vocea.app/mcp-serverofficial
AlicenseAqualityCmaintenanceEnables AI agents to generate speech, transcribe audio, and manage voices via the Vocea API.6MIT
TDQS
Scored across 29 tools
Several tools overlap in purpose: generate_get-generation and generations_get-by-id both retrieve a generation, generate_estimate-cost and generations_estimate-cost both estimate cost, and create-lipsync vs generate_create-generation have overlapping creation flows. The upload-related tools (open-upload-widget, upload-media, assets_create-upload-url) also occupy similar territory, though their descriptions try to differentiate use cases.
Tool names are highly inconsistent, mixing hyphens and underscores (create-lipsync vs generate_create-generation), using both resource-first and verb-first patterns (generate_get vs generations_get-by-id), and switching prefixes for the same resource (generate_ vs generations_). This makes the naming pattern unpredictable and confusing.
With 29 tools, the server feels heavy. Redundancy inflates the count: two cost-estimate tools and two get-generation tools do the same thing. While the domain is broad, several tools could be consolidated, making 29 unnecessarily unwieldy.
The tool set covers the main domain well: full CRUD for assets and projects, generation lifecycle (create, get, list, estimate, delete), voice cloning and management, and TTS. Minor gaps exist (no voice update, no generation cancellation), but agents can accomplish most workflows without dead ends.