mcp-imagetovideoai-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| image_to_video_build_promptA | Build a production-ready image-to-video prompt from subject motion, environment, camera, lighting, timing, and constraints. |
| image_to_video_planA | Create a concise shot plan for turning a still image into a short video, including motion hierarchy and iteration checks. |
| image_to_video_get_startedA | Return the appropriate Image to Video AI workspace URL and a preflight checklist. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
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.
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.
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.
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.