move-api-mcp
Related Servers
Alternatives to move-api-mcp
No user-submitted related servers found.
Related Servers
FlicenseNot gradedqualityCmaintenanceEnables image, video, and audio generation via Magic Hour's API, including async polling, file uploads, and project downloads.6-- AlicenseAqualityAmaintenanceEnables creating and polling Luma video modification tasks, fetching task status, and checking pricing via the RunAPI API.449 npmApache 2.0
- FlicenseAqualityBmaintenanceEnables discovering and invoking all 97 published Frame.io V4 API operations through a searchable catalog, covering accounts, projects, folders, files, comments, shares, metadata, webhooks, and more using OAuth credentials. It also performs complete local multipart uploads, including chunked PUTs and upload status checks.5-

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.11659 npmMIT- FlicenseNot gradedqualityCmaintenanceEnables video generation through ComfyUI workflows, providing tools to list workflows, create and manage video jobs, upload assets, and retrieve results.-
- AlicenseBqualityBmaintenanceEnables AI agents to create lipsync videos, manage assets, and check generation status via the Sync API.2913 npm1MIT
TDQS
Scored across 26 tools
Tools are mostly organized by resource and action, making takes, jobs, volumes, and files easy to distinguish. The only real confusable pairs are create_file/upload_file and get_file/download_file, though their descriptions clarify the intended use.
Nearly every tool follows a clear move_<verb>_<noun> pattern with consistent snake_case. Minor deviations like move_client_info and move_graphql break the pattern slightly, but the overall style is predictable.
With 26 tools, the server is on the heavy side, and the many file/job variants make the surface feel crowded. However, the tools map to a genuinely broad API spanning clients, files, takes, jobs, volumes, and webhooks, so the count is not an extreme mismatch.
The core file-to-take-to-job-to-output workflow is well covered, including multicam volume calibration and webhook setup. Notable gaps remain: there is no list-files tool, no delete/cancel operations for takes or jobs, and volume update/delete coverage is absent.