hailuo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUNAPI_API_KEY | Yes | Your RunAPI API key. Can also be set via config file at ~/.config/runapi/config.json. |
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
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| loginA | Authenticate RunAPI by opening a browser PKCE login flow and saving the API key to ~/.config/runapi/config.json. |
| image_to_videoB | Create a Hailuo task on RunAPI (image to video). Returns a task id, status, and output URLs. |
| text_to_videoB | Create a Hailuo task on RunAPI (text to video). Returns a task id, status, and output URLs. |
| get_taskB | Fetch the current status and latest result payload for a hailuo task. |
| check_pricingC | Look up RunAPI pricing for the hailuo model line. |
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 5 tools
Each tool has a clearly distinct purpose: two generation tools differ by input modality (image_to_video vs text_to_video), get_task handles retrieval, and login/check_pricing are distinct utilities. There is no meaningful overlap that would cause misselection.
Almost all tools use snake_case with a verb_noun or noun_to_noun structure (check_pricing, image_to_video, text_to_video, get_task), which is readable and consistent. 'login' is a bare verb that breaks the noun pattern slightly, but this is a conventional deviation.
Five tools is well-scoped for a video-generation service, with each tool earning its place: auth, pricing, two generation modes, and task polling. Nothing feels redundant or missing from the count perspective.
Core lifecycle is covered: login, check pricing, create tasks in both modes, and poll task status/results. Minor gaps exist such as no task cancellation or listing of prior tasks, but the primary workflow is complete.