Happyhorse Mcp

io.github.runapi-builderPublished by GitHub account runapi-builderv0.2.2Updated Oct 29, 2026

RunAPI MCP server for HappyHorse: create tasks, poll status, check pricing.

VerifiedSTDIODesktop onlyMedia & DesignAI & ML

Overview

AI-generated overview

RunAPI MCP server scoped to the HappyHorse video model line: create video generation tasks, poll results, and check pricing.

What you can do
  • Create HappyHorse video tasks: text to video, image to video, and video editing, each returning a task id, status and output URLs
  • Poll an existing task for its current status and latest result payload
  • Look up RunAPI pricing for HappyHorse models and endpoints, available before sign-in
  • Optionally wait for a task to finish, or submit without waiting and check back later
  • Authenticate through a browser login flow that saves the RunAPI key to a local config file
When to use it
Use it when an assistant should generate or edit video through RunAPI's HappyHorse models and stay scoped to that model line rather than the full RunAPI catalog. It suits workflows where the agent checks pricing, submits a task, and reports back task ids and output URLs.
Requirements
Runs locally over stdio, typically started with npx from the npm package, so Node.js is needed. A RunAPI account and API key are required for task creation and status polling: either the RUNAPI_API_KEY environment variable for headless or CI hosts, or the login tool, which opens a browser and writes the key to a local RunAPI config file. Pricing lookup works without a key. Network access to RunAPI is required.
Before you install
Task creation spends money on RunAPI, so confirm cost and scope before expensive, long-running or batch requests; the server's own instructions ask assistants to confirm such requests. The login tool stores an API key in a local config file, and the README warns not to commit real keys. Creating tasks sends prompts and media to RunAPI as a third party, and generated media is not inspected by the assistant.

Installation

In SourceWeft

  1. Open Happyhorse Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

RunAPI HappyHorse MCP Server

HappyHorse API access for AI agents: run video generation operations, poll asynchronous results, and check pricing through one focused MCP server.

Works with Claude Code, Codex, Cursor, Windsurf, VS Code, Roo Code, and any MCP-compatible host.

[npm version] [GitHub repository] [Apache-2.0 license] [MCP Server] [7 models]

Install | Tools | Models | Agent Prompts | Configuration | Links


Why This Package?

@runapi.ai/happyhorse-mcp is a focused Model Context Protocol server for the HappyHorse model line on RunAPI. It gives MCP-compatible assistants direct access to 3 endpoints and 7 model variants without loading the full RunAPI catalog.

Use this per-model server when an agent should stay scoped to HappyHorse. Use @runapi.ai/mcp when one assistant should discover every RunAPI model line.


Install

Add it to Claude Code:

bash
claude mcp add happyhorse -s user -- npx -y @runapi.ai/happyhorse-mcp

Use project scope when the server should be shared with a repository:

bash
claude mcp add happyhorse -s project -- npx -y @runapi.ai/happyhorse-mcp

Codex, Cursor, Windsurf, VS Code, Roo Code, and other MCP hosts can use the same stdio command:

json
{  "mcpServers": {    "happyhorse": {      "command": "npx",      "args": ["-y", "@runapi.ai/happyhorse-mcp"]    }  }}

check_pricing works before sign-in. For task creation and status polling, ask your assistant to call the login tool. It opens a browser login and saves credentials to ~/.config/runapi/config.json, the same file used by runapi login. Headless and CI hosts can still set RUNAPI_API_KEY before starting the MCP host.

Ready-made examples are in examples/ for Claude, Cursor, Windsurf, VS Code, and Roo Code.


Tools

ToolAuthPurpose
edit_videoYesCreate a HappyHorse edit video task and optionally wait for a terminal status. Returns the task id, status, and output URLs.
image_to_videoYesCreate a HappyHorse image to video task and optionally wait for a terminal status. Returns the task id, status, and output URLs.
text_to_videoYesCreate a HappyHorse text to video task and optionally wait for a terminal status. Returns the task id, status, and output URLs.
get_taskYesFetch the current status and latest payload for an existing task.
check_pricingNoLook up current pricing for a HappyHorse model and endpoint.

Models

HappyHorse covers 7 model variants across 3 endpoints. Each tool accepts the models listed for it:

ToolModels
edit_videohappyhorse-edit-video
image_to_videohappyhorse-1.0-i2v, happyhorse-image-to-video
text_to_videohappyhorse-1.0-r2v, happyhorse-1.0-t2v, happyhorse-character, happyhorse-text-to-video

Model availability can change between releases. Use check_pricing or the HappyHorse model page for the current catalog view.


Agent Prompts

Ask your assistant in natural language; it can inspect pricing, create the task, and return the task id plus output URLs.

Create a task

text
Run a HappyHorse edit video task with RunAPI.

The assistant can call check_pricing, then edit_video, and return the task id, status, and output URLs.

Submit without waiting

text
Create the task but don't wait for it to finish.

The assistant calls the create tool with wait: false and returns the task id. Check on it later with get_task.

Check pricing before creating

text
Check current HappyHorse pricing, then create the task if it matches my request.

The assistant calls check_pricing and can link to the HappyHorse model page for the canonical catalog entry.


Configuration

The server resolves auth in this order:

  1. RUNAPI_API_KEY environment variable, useful for headless and CI hosts
  2. ~/.config/runapi/config.json, created by the MCP login tool or runapi login
  3. No key, which still allows check_pricing

The config file is normally managed by login. A pre-provisioned headless config can use:

json
{  "apiKey": "your_runapi_key"}

Do not commit real API keys.


Links

ResourceURL
HappyHorse model pagehttps://runapi.ai/models/happyhorse
npm package@runapi.ai/happyhorse-mcp
GitHub repositoryrunapi-ai/happyhorse-mcp
RunAPI MCP overviewrunapi.ai/mcp
RunAPI docsrunapi.ai/docs

License

Licensed under the Apache License, Version 2.0.

Source: README.md at commit a25f3f3

Tools

6

login

Authenticate RunAPI by opening a browser PKCE login flow and saving the API key to ~/.config/runapi/config.json.

Parametersforce

edit_video

Create a HappyHorse task on RunAPI (edit video). Returns a task id, status, and output URLs.

Parametersseedwaitmodelprompttimeout_mscallback_urlaudio_settingpoll_interval_mssource_video_urlrequiredoutput_resolutionreference_image_urls

image_to_video

Create a HappyHorse task on RunAPI (image to video). Returns a task id, status, and output URLs.

Parametersseedwaitmodelprompttimeout_mscallback_urlduration_secondspoll_interval_msoutput_resolutionfirst_frame_image_urlrequired

text_to_video

Create a HappyHorse task on RunAPI (text to video). Returns a task id, status, and output URLs.

Parametersseedwaitmodelprompttimeout_msaspect_ratiocallback_urlduration_secondspoll_interval_msoutput_resolutionreference_image_urls

get_task

Fetch the current status and latest result payload for a happyhorse task.

Parametersactionrequiredtask_idrequired

check_pricing

Look up RunAPI pricing for the happyhorse model line.

Parametersmodelaction

Version history

4
  1. v0.2.2LatestOct 22, 2026
  2. v0.2.1Oct 15, 2026
  3. v0.2.0Sep 30, 2026
  4. v0.1.8Sep 16, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts