Movoa MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MOVOA_API_KEY | Yes | Your Movoa API key, created at movoa.ai/settings/apikeys. Required to run tools; listing tools needs no key. | |
| MOVOA_BASE_URL | No | Overrides the endpoint; only useful against a local build of the site. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_videoA | Generate a video clip with sound from a text prompt on movoa.ai, or animate a photo by passing image_url (photo to video). Defaults to MiniMax H3 at 480p. Runs cost credits on your Movoa account, at the prices on https://movoa.ai/pricing. Video takes minutes: by default this returns a run id to poll with check_status. |
| check_statusA | Read the status of a run started with generate_video, and the video URL when it is ready. |
| creditsB | The credits left on the Movoa account behind MOVOA_API_KEY. Free to call. |
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 targets a clearly different concern: starting a generation, polling a run, and checking account credits. There is no plausible way to confuse them, and the async generate/check pair is explicitly linked in the descriptions.
check_status and generate_video follow a consistent verb_noun snake_case pattern, while credits is a bare noun. The deviation is readable and arguably natural for an account-balance query, but it does break the pattern.
Three tools is lean but well-matched to a focused async video-generation API: submit, poll, and check balance. Nothing feels redundant, though the surface is minimal enough that a couple more lifecycle tools would not feel heavy.
The core lifecycle is covered: generate_video returns a run id, check_status polls and surfaces the resulting URL, and credits covers billing concerns. Gaps are minor — no way to list past runs, cancel an in-flight run, or retrieve failure details beyond status.