Seedance Polza MCP Server
Related Servers
Alternatives to Seedance Polza MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables video generation from text prompts or images using Agnes AI's video models, with async task submission and status polling.210 npm1MIT
- FlicenseAqualityDmaintenanceEnables video generation using the Seedance 2.0 model through MCP, supporting both OpenAI and Volcengine API formats with tools for creating, monitoring, and downloading videos.6-
- FlicenseAqualityDmaintenanceEnables generating videos from images and text prompts using Jimeng Video 3.0 API, supporting 5s/10s durations and automatic result polling.3-
- AlicenseAqualityBmaintenanceByteDance Seedance AI video generation with text-to-video, image-to-video, multiple models (1.5 Pro/1.0 Pro/Lite), synchronized audio, and flexible resolutions up to 1080p.7163 PyPI18MIT
- AlicenseAqualityBmaintenanceGenerate video from a prompt, from an image, or from up to thirty reference images, routed across the field of AI video models (Sora, Veo, Kling, Seedance, Hailuo, Wan and more). Quotes the credit cost before spending it and refunds a technical failure automatically.5MIT
- AlicenseAqualityAmaintenanceEnables creating text-to-video tasks using Seedance models, polling task status, and checking pricing via a single RunAPI API key.449 npmApache 2.0
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: guide for instructions, create for initiating generation, get_status for one-time status check, and wait_for_completion for polling until done. No overlap or ambiguity between them.
All tool names follow a consistent pattern: 'seedance_' prefix followed by verb_noun (model_guide, create_video, get_status, wait_for_completion). The naming is uniform and predictable.
With only 4 tools, the server is tightly scoped for its purpose of video generation via Seedance. Each tool is essential and there are no redundant or unnecessary additions, making the count appropriate.
The server covers the core lifecycle of video generation: guidance, creation, status checking, and waiting for completion. While a cancel or list operation could be imagined, they are not essential for the primary workflow, so the set is nearly complete.