volcengine-imagegen-mcp
Related Servers
Alternatives to volcengine-imagegen-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server for generating images and videos using Volcengine's Jimeng APIs, supporting text-to-image, image-to-image, multi-image fusion, text-to-video, and image-to-video.31MIT
- AlicenseAqualityDmaintenanceMCP server for generating images using Volcano Engine's Jimeng AI, supporting the latest Seedream4.0 model.16 npm2MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server providing multi-modal generation tools based on Volcengine's Jimeng AI, supporting high-quality 4K image creation, intelligent image editing, and video generation. It enables users to perform complex visual tasks directly within clients like Cursor and Claude Desktop.6 npmMIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that generates high-quality images through Volcano Engine's Doubao model, supporting bilingual prompts, multiple resolutions, and parameter controls like seed and guidance scale.2MIT
- AlicenseAqualityCmaintenanceMCP server for generating and editing images and videos via DashScope/OpenAI-compatible APIs, with tools for text-to-image, image editing, text/video generation, and automatic local download.5MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that integrates with Volcengine's coding API to enable AI-powered chat, file read/write, and command execution via OpenClaw.MIT
TDQS
Scored across 4 tools
Most tools are clearly distinct: generate_image handles text-to-image, image_to_image handles image-to-image, and list_models provides model metadata. However, generate_image_set overlaps with generate_image since it is described as generating multiple related images via repeated calls, potentially causing occasional misselection.
Tool names mix conventions: generate_image and generate_image_set follow a verb_noun pattern, list_models also follows verb_noun, but image_to_image uses a noun_to_noun structure. This inconsistency is noticeable but still readable and understandable.
With only 4 tools, the server is well-scoped for an image generation service. Each tool serves a clear purpose without unnecessary bloat, and the count aligns well with the domain.
The tool surface covers core image generation workflows: text-to-image, image-to-image, batch generation, and model discovery. Minor gaps exist, such as lack of explicit image variation or style transfer, but these are not critical and can be worked around with existing tools.