seedream-mcp
Related Servers
Alternatives to seedream-mcp
No user-submitted related servers found.
Related Servers
- 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
- AlicenseAqualityAmaintenanceEnables creating and managing Runway video generation tasks (text-to-video, video extension) through a single RunAPI key, including task polling and pricing checks.538 npmApache 2.0
- AlicenseBqualityAmaintenanceEnables AI image and video generation tasks (text-to-image, image-to-video, edit, upscale, etc.) via RunAPI, with support for polling and pricing lookups.10239 npmApache 2.0
- AlicenseBqualityAmaintenanceEnables creating and managing GPT Image tasks (edit and text-to-image) via RunAPI, with options to poll status and check pricing.594 npmApache 2.0
- AlicenseBqualityAmaintenanceEnables users to create image editing and text-to-image tasks, poll their status, and check pricing for the Nano Banana model line through a RunAPI API key.5218 npmApache 2.0
- FlicenseAqualityBmaintenanceEnables text-to-image generation via RunningHub's seedream-v5-lite model, with support for submitting tasks and polling for results.3-
TDQS
Scored across 6 tools
The creation tools (text_to_image, edit_image, decompose_layers) are distinct in purpose, though all share similar descriptions. get_task, login, and check_pricing are clearly separate, but the three creation tools could be confused if the descriptions were less clear about their specific operations.
Tool names use a consistent snake_case verb_noun pattern (e.g., 'get_task', 'edit_image', 'check_pricing'). The only minor deviation is 'login' (a single verb) and 'decompose_layers' (verb with object but not a standard CRUD noun). Overall, the pattern is predictable.
With 6 tools, the count is well within the ideal range for a focused server. Each tool covers authentication, task creation, status checking, and pricing, which is reasonable for the scope. No redundancy or bloat is apparent.
The server covers the core lifecycle of creating tasks, checking results, and authenticating, but it lacks a cancellation or listing operation. Users cannot list all tasks or cancel a task, which could be a gap for an agent managing multiple tasks. However, for simple workflows, the core is sufficient.