Independent Video Generator
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Independent Video Generator
This is a standalone video generation frontend and backend extracted from the main project. It only keeps the ComfyUI video workflow and does not include Agent conversations or image generation.
Startup
Copy
.env.exampleto.envand verify the ComfyUI and FFPROBE paths.Install dependencies:
npm installDevelopment mode:
npm run devProduction build:
npm run buildProduction start:
npm run start
Default URL: http://127.0.0.1:8834
Windows users can simply double-click start.bat; it will automatically switch to the current folder, create .env, install dependencies, and start the service.
Related MCP server: ComfyUI MCP Server
Video API
GET /api/video/workflowsPOST /api/video/jobsGET /api/video/jobs/:jobIdDELETE /api/video/jobs/:jobId
MCP Minimal Version
Start the video API first, then run npm run mcp. The MCP server uses stdio transport and calls the existing video API through MCP_API_URL (default http://127.0.0.1:8834).
Provided tools:
list_video_workflowscreate_video_jobupload_video_assetget_video_joblist_video_jobsget_video_resultcancel_video_job
Remote frontend and GPU host
Keep the frontend and MCP on the portable control side, and keep Backend, ComfyUI, models, and GPU on the same GPU host. Build the frontend with:
VITE_BACKEND_URL=http://GPU_HOST:8834Configure the GPU host Backend with:
HOST=0.0.0.0
PORT=8834
COMFYUI_URL=http://127.0.0.1:8188
CORS_ORIGIN=http://FRONTEND_HOSTConfigure MCP with:
MCP_API_URL=http://GPU_HOST:8834The browser and MCP call only the Video Generator API; ComfyUI remains private on the GPU host. API key authentication is not enabled yet, so HOST=0.0.0.0 should only be used on a trusted LAN or VPN.
Currently, images and audio are still transmitted as data URLs, which is suitable for a local MVP but not for large or multi-user deployments.
Video workflow assets are located in workflow/. This project currently shares the same ComfyUI service as the main project, but the code, frontend pages, job API, and workflow JSON are independent.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
LLM chat, text tools, image generation, editing, batch image jobs, and asynchronous video generation
Remote MCP for RunComfy: ComfyUI deployments, hosted models, LoRA training. 31 tools.
Create and manage cinematic AI video renders through the Future Video Studio Agent API.
Create AI images and videos, manage projects and credits, and use workspace campaign context.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables generation of AI videos and images using RunComfy APIs. Supports multiple models for text-to-video, image-to-video, text-to-image, and image-to-image workflows with customizable parameters like aspect ratio, duration, and seed.-
- AlicenseNot gradedqualityDmaintenanceDynamically loads ComfyUI workflows as MCP tools, enabling AI assistants to generate images, videos, and audio by executing workflows across categories like text-to-image, image-to-video, and text-to-audio with automatic parameter mapping and progress monitoring.3MIT
- AlicenseNot gradedqualityCmaintenanceTurns curated ComfyUI workflows into typed MCP tools and REST endpoints, enabling image generation and job management through natural language or HTTP calls.MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to remotely control a ComfyUI installation via its HTTP API, including generating and editing images, creating transparent assets, generating video and audio, tracking the queue, and downloading results.20MIT