byteplus-image-mcp
Related Servers
Alternatives to byteplus-image-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables generating AI images using BytePlus Seedream models (4.5 and 5.0 Lite) via natural language, supporting text-to-image, reference-based editing, and sequential multi-panel sets.-
- AlicenseNot gradedqualityDmaintenanceEnables AI-powered image generation using Volcano Engine's SeeDream 4.0 model. Supports custom sizes, reference images, and automatic prompt generation without complex prompting.7 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI image generation using Volcano Engine's Seedream 4.0 API with text-to-image, image-to-image, multi-image fusion capabilities, built-in prompt templates, and automatic cloud storage integration.19MIT
- FlicenseBqualityDmaintenanceEnables AI-powered text-to-image generation using Volcengine's API with support for multiple image sizes, customizable parameters like guidance scale and seed, and flexible output formats.1-
- AlicenseAqualityCmaintenanceEnables AI image generation using Doubao Seedream models and video generation using Doubao Seedance models through Volcano Engine's API, supporting text-to-image, image-to-image, text-to-video, and task status queries.317 npm3MIT
- AlicenseAqualityBmaintenanceEnables text-to-image generation using Alibaba Cloud's Qwen-Image models, supporting both synchronous and asynchronous modes with configurable parameters.4MIT
TDQS
Scored across 2 tools
byteplus_generate_image is solely responsible for creating images, while byteplus_list_models handles model discovery and quota information. There is no functional overlap between the two tools.
Both tool names follow the same byteplus_verb_noun pattern: generate_image and list_models. The naming is consistent, predictable, and clearly conveys each tool's action.
With only two tools, the server is slightly under the typical 3-15 range, but the count is reasonable for a narrow image-generation purpose. Each tool earns its place: generation is the core action, and model listing supports informed model selection.
For the server's stated purpose of text-to-image generation, the surface is complete: list_models lets an agent choose the right model, and generate_image produces the image with appropriate parameters. There are no obvious dead ends in the core workflow.