AI Video Generator MCP 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate-videoB | Generate a video from text prompt and/or images using AI models (Luma or Kling) |
| check-video-statusC | Check the status of a video generation request |
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 2 tools
The two tools have completely distinct purposes with no overlap: one checks status of existing requests, the other creates new videos. An agent would never confuse these functions as they operate on different stages of the video generation workflow.
Both tools follow a consistent verb-object naming pattern with hyphen separation: 'check-video-status' and 'generate-video'. The naming is predictable and follows the same convention throughout the set.
With only 2 tools for a video generation server, the surface feels severely limited. While the basic create+status pair covers minimal functionality, a video generation domain typically requires more operations like listing videos, canceling generations, or managing templates. The count is too low for the apparent scope.
The toolset provides only generation initiation and status checking, creating significant gaps. Missing are operations like listing existing videos, canceling pending generations, retrieving generated content, managing templates/presets, or configuring generation parameters. Agents will hit dead ends when trying to manage the video lifecycle beyond initial creation.