H3 Cloud MCP
Related Servers
Alternatives to H3 Cloud MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables driving a self-hosted ComfyUI instance over stdio MCP for image and song generation, workflow execution, job and queue management, and local model, asset, and workflow administration. Every submit is priced against the machine's own VRAM meter first, so work the GPU cannot pay for is refused before it is sent, and an unreadable meter also refuses rather than permitting.Business Source 1.1
- AlicenseAqualityCmaintenanceEnables standard stdio MCP hosts to drive a local ComfyUI installation for prompt-based image generation, task status/result retrieval, environment inspection, and VRAM release.4MIT
- AlicenseAqualityBmaintenanceMCP server for MiniMax H3 multimodal video generation. Enables text-to-video, image-to-video, and audio-guided video creation with async task retrieval and batch processing.10338 PyPI2MIT
- AlicenseNot gradedqualityDmaintenanceLocal-first MCP server for controlling a loopback ComfyUI instance from same-machine or authenticated LAN clients.MIT
- AlicenseAqualityDmaintenanceEnables MCP clients to generate images, speech, music, video, and 3D meshes via a remote mlx-serve instance on Apple Silicon.10Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to connect to and interact with ComfyUI for workflow execution and image generation.Apache 2.0
TDQS
Scored across 12 tools
The set contains two parallel stacks (h3_art_* for managed AutoDL Art and h3_* for the private ComfyUI tunnel), producing near-duplicate tools like h3_art_job_status/h3_job_status and h3_art_download_video/h3_download_video. Descriptions clarify the managed vs. private distinction, but an agent must read carefully to avoid picking the wrong backend.
All names are snake_case with an h3_ prefix, but the naming mixes noun-first forms (h3_art_job_status, h3_job_status) with verb-first forms (h3_check_backend, h3_generate, h3_cancel_job). The two prefix families are predictable internally, yet the overall convention is not uniform.
12 tools is well within a reasonable range for a video-generation server covering quote, generate, status, download, and cancel flows. There is some duplication from maintaining both managed and private backends, but each tool is plausibly needed.
Core lifecycle is covered: pricing quotes, workflow discovery, generation, job status, download, and cancellation, plus backend health checking. Minor gaps exist, such as no explicit cancellation for managed AutoDL Art jobs and no job-listing operation.