@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_videoB | Create a HappyHorse task on RunAPI (edit video). Returns a task id, status, and output URLs. |
| image_to_videoC | Create a HappyHorse task on RunAPI (image to video). Returns a task id, status, and output URLs. |
| text_to_videoC | 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_pricingB | 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 targets a clearly distinct operation: three video creation modes based on input type (edit, image-to-video, text-to-video), task status retrieval, pricing lookup, and authentication. There is no overlap or ambiguity between tools.
All names use consistent snake_case with verb-based naming. 'login' is the only tool that does not follow a verb_noun pattern, which is a minor deviation but still clear.
Six tools cleanly cover the essential workflow: three generation modes, status checking, pricing, and authentication. The count is well-scoped with no redundant or unnecessary tools.
The core create-and-poll workflow is fully supported. However, task lifecycle operations like listing, cancelling, or deleting tasks are missing, and pricing is only available for the model line, leaving minor gaps.