A
licenseB
qualityB
maintenanceA production-minded Model Context Protocol server for Adobe After Effects that enables AI agents to control motion graphics, editorial planning, and rendering.
48
17 npm
4
MIT
mcp-imagetovideoai-server
Related Servers
Alternatives to mcp-imagetovideoai-server
No user-submitted related servers found.
Related Servers
studio-stateofficial
AlicenseNot gradedqualityDmaintenanceA stateless MCP server for AI film and video production that tracks project state, shot status, and updates, enabling consistent characters and continuity across generative video tools.MIT- FlicenseNot gradedqualityDmaintenanceA powerful Model Context Protocol (MCP) server for image processing, designed to empower AI models with advanced image manipulation capabilities.-
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that connects multiple AI models into a single workflow, enabling multi-model orchestration, conversation continuity, and tools like code review, planning, and CLI-to-CLI bridging.-
- AlicenseBqualityFmaintenanceModel Context Protocol server that enables generating videos from text prompts and/or images using AI models (Luma Ray2 Flash and Kling v1.6 Pro) with configurable parameters like aspect ratio, resolution, and duration.23MIT
- FlicenseNot gradedqualityCmaintenanceModel Context Protocol server that exposes ComfyUI workflows as tools, enabling chat agents to generate images, video, audio, and 3D content.-
TDQS
A4/5.0
Scored across 3 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: build_prompt creates a text prompt, plan creates a structured shot plan, and get_started provides a URL and checklist. There is no overlap or ambiguity among them.
Naming Consistency4/5
All tools share the consistent 'image_to_video_' prefix and use lowercase, underscore-separated verbs. Minor structural variation exists (build_prompt has an object, plan is a single verb, get_started is a phrasal verb), but the overall pattern is predictable and readable.
Tool Count5/5
With only 3 tools, the server is tightly scoped to its purpose. Each tool covers a necessary step in the image-to-video workflow, and the count is within the ideal 3-15 range for a specialized server.
Completeness5/5
The server covers the full intended workflow for its helper role: onboarding (get_started), planning (plan), and prompt creation (build_prompt). There are no obvious missing operations given its stated purpose as a prompt/plan assistant rather than the actual generation engine.
Maintenance
ActivitySlowing
ResponsivenessNo issues