@runapi.ai/happyhorse-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUNAPI_API_KEY | Yes | Your RunAPI API key. Get one at https://runapi.ai. |
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. |
| edit_videoC | Create a HappyHorse task on RunAPI (edit video). Returns a task id, status, and output URLs. |
| image_to_videoB | Create a HappyHorse task on RunAPI (image to video). Returns a task id, status, and output URLs. |
| text_to_videoB | Create a HappyHorse 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 happyhorse task. |
| check_pricingA | Look up RunAPI pricing for the happyhorse 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 6 tools
Each tool has a clearly distinct purpose: authentication, three video generation modes, task status retrieval, and pricing lookup. No two tools overlap in functionality.
The naming pattern is mostly verb_noun (e.g., get_task, check_pricing) but the video generation tools break this with image_to_video and text_to_video, while edit_video fits the verb pattern. The mix is still readable and predictable in context.
With 6 tools, the server is well-scoped for video generation and task management. Each tool covers a necessary part of the workflow without unnecessary bloat.
The surface covers login, task creation, status retrieval, and pricing. A task listing or cancellation tool would be a minor addition, but the primary use cases are fully supported.