Skip to main content
Glama
README.md
# Image to Video AI MCP Server

A lightweight Model Context Protocol server for planning image-to-video shots, building production-ready motion prompts, and preparing reliable generation workflows.

## Installation

Run directly with npx:

```bash
npx -y mcp-imagetovideoai-server
```

Or install globally:

```bash
npm install -g mcp-imagetovideoai-server
```

## MCP Configuration

```json
{
  "mcpServers": {
    "image-to-video-ai": {
      "command": "npx",
      "args": ["-y", "mcp-imagetovideoai-server"]
    }
  }
}
```

## Tools

### `image_to_video_build_prompt`

Builds a structured motion prompt from the subject, primary motion, environment, camera, lighting, timing, style, and artifact constraints.

Required inputs:

- `subject`
- `motion`

### `image_to_video_plan`

Creates a concise shot plan with motion hierarchy, camera guidance, continuity checks, optional end-frame control, and an iteration strategy.

Required inputs:

- `goal`
- `image_description`

### `image_to_video_get_started`

Returns a localized workspace URL and a short preflight checklist. Supported locales are English (`en`), Japanese (`ja`), and Chinese (`zh`).

## Example

Ask your MCP client:

```text
Build a five-second prompt for a product photo. The bottle should rotate slowly,
the camera should make a subtle dolly-in, and the label must remain stable.
```

Use the resulting plan with the [Image to Video AI generator](https://imagetovideoai.pro/) to create and iterate on the clip.

## Scope

This package prepares prompts and shot plans. It does not request account credentials, store API keys, upload source media, or claim to call a private generation API.

## License

MIT

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