jimeng-web-mcp
Related Servers
Alternatives to jimeng-web-mcp
No user-submitted related servers found.
Related Servers
- AlicenseDqualityDmaintenanceIntegrates Jimeng AI image and video generation services through MCP protocol, enabling users to generate high-quality images and videos from text prompts with support for image mixing, reference images, and multiple AI models.39 npm53MIT
- AlicenseNot gradedqualityFmaintenanceEnables AI-powered multimodal content generation using Volcano Engine's Jimeng AI, supporting text-to-image, text-to-video, and image-to-video conversion with customizable parameters.18 npm29MIT
- FlicenseAqualityDmaintenanceEnables generating videos from images and text prompts using Jimeng Video 3.0 API, supporting 5s/10s durations and automatic result polling.3-
- AlicenseAqualityDmaintenanceWraps Jimeng AI's image and video generation APIs for AI assistants to create and edit visual content via natural language.91MIT
- AlicenseNot gradedqualityCmaintenanceEnables image generation using Jimeng AI (Doubao Seedream 4.0) via APICore, supporting text-to-image, image-to-image, multi-image fusion, and batch generation.2MIT
- FlicenseNot gradedqualityCmaintenanceA Model Context Protocol server for AI image and video generation using Jimeng AI, enabling text-to-image, image composition, text-to-video, and image-to-video through Claude Desktop and other MCP clients.78-
TDQS
Scored across 8 tools
Each tool serves a distinct purpose: ping checks connectivity, image and image_batch handle single vs. series generation, query fetches task status, and video, video_frame, video_multi, and video_mix cover different video generation modes. The video tools could cause some confusion since they all generate videos, but their input differences are clearly described.
Video tools share a consistent 'video' prefix, and image tools have a clear 'image' base. However, ping and query are verbs while image and video are nouns, and video_mix uses a verb suffix, causing a mix of conventions that is still readable but not fully predictable.
With 8 tools covering both image and video generation plus a status query, the server is well-scoped. Each tool has a distinct role, and the count is within the ideal 3-15 range, neither too sparse nor overloaded.
The core lifecycle of generation and result retrieval is covered for both images and videos. Minor gaps exist, such as no explicit tool for image editing (e.g., inpainting) or listing available models, but these are non-essential for a basic generation workflow.