OpenDaemon ComfyUI MCP
Related Servers
Alternatives to OpenDaemon ComfyUI MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceAI-native timeline editor for short-form video. Your agent cuts, captions, adds motion graphics and renders against a real, editable timeline over MCP — not a render queue. Human-in-the-loop by design: it calls request_review and waits while you supervise in a browser. Local-first and AGPL; your footage never leaves your machine.2AGPL 3.0

Treza MCPofficial
AlicenseNot gradedqualityBmaintenanceBuild, run, schedule, and publish AI video pipelines to YouTube and TikTok. Frontier video, image, voice, and text models on a node canvas, over MCP.28 npmMIT- AlicenseAqualityBmaintenanceWraps ComfyUI to generate images, video, and upscales from text prompts via MCP tools, providing a curated workflow interface without the node editor.83MIT
- AlicenseCqualityBmaintenanceOpen-source local-first AI media workbench with Canvas, video editor, Assets, and MCP control.38367Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to drive an AI video production studio, orchestrating character and scene continuity, text-to-speech, ComfyUI video generation, lip-sync, VLM quality review, provenance tracking, and OpenTimelineIO export.Apache 2.0
- FlicenseNot gradedqualityDmaintenanceLocal-first AI video editing engine controlled by MCP-compatible AI hosts, enabling AI to inspect footage, propose edits, modify multitrack projects, and render locally while keeping user control.-
TDQS
Scored across 67 tools
Tools are grouped into clear domains (render, queue/system, model management, editing, workflows, audio) and most have distinct, well-explained purposes. The main overlaps are intentional convenience layers: render vs rerender vs render_batch vs render_variations, and build_video vs the individual join_clips/add_voice/add_captions/export tools, which could make an agent hesitate about which path to take. add_text vs title_card vs add_captions vs add_logo are also similar enough to require reading descriptions carefully.
The dominant pattern is verb_noun (render_batch, delete_video, list_models, add_voice, check_workflow), applied consistently across most of the surface. Some noun-only outliers exist (queue, estimate, render, thumbnail, boomerang, export, fade, title_card, job_status), but they are readable and each denotes a single unambiguous operation.
67 tools is heavy for a single server, even one covering a full video pipeline from model download to platform export. Several tools could be folded into aggregates that already exist (build_video already combines join/caption/voice/export), so the set feels broader than strictly necessary. The breadth is somewhat justified by the domain, but it is at the upper edge of what an agent can navigate comfortably.
Coverage is impressive: model install/check, rendering, batching, queue control, diagnostics, editing, audio/voice, captions, workflows, and platform export are all present with no obvious dead ends for the core workflow. Minor gaps remain, such as deleting or renaming saved workflows, and job history beyond the last 10 entries.