runapi-ai/mcp

AI image generation, video generation, music creation, text-to-speech, prompt search, and model discovery — 160+ executable models across 4 modalities in one MCP server.
Works with Claude Code, Codex, Cursor, Windsurf, VS Code, Roo Code, and any MCP-compatible host.
Quick Start |
Tools |
Examples |
Catalog |
Platforms
---
What Is This?
RunAPI MCP Server connects MCP-compatible coding tools to RunAPI.
It lets an assistant browse the RunAPI catalog, inspect model inputs, check current runtime pricing, create media tasks, poll task status, and check account balance.
The discovery tools work without an API key because they use the embedded build-time catalog.
Authenticated operations use the login tool, runapi login, RUNAPI_API_KEY, or shared RunAPI config.
This package is a pure client.
It does not run a local generation backend and only needs RunAPI sign-in for authenticated tools.
---
Hosted MCP
Remote MCP clients can connect directly to:
No Node.js installation is required. Use OAuth when the client supports remote MCP authorization, or configure a RunAPI API key as the bearer credential. See the Hosted MCP setup page for Cursor, Claude Desktop, VS Code, and Windsurf configurations.
Hosted MCP exposes the eight Business Tools documented below. Local Login remains available only in the Local MCP package.
---
Quick Start
For Local MCP over stdio, install RunAPI with Claude Code's MCP command:
The scope flag controls where the MCP server is stored:
- -s user: global, available in all projects for your user.
- -s project: team-shared, written to .mcp.json in the current repo so it can be committed.
Use project scope when you want the whole team to share the same server config:
Compatibility fallback for non-Claude Code platforms or manual JSON config:
If your host needs a generated config file, use the legacy init command as a fallback:
Free catalog tools work before sign-in.
For task creation, task status, and balance checks, 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.
---
Tools
| Tool | Auth | Purpose |
|---|---|---|
| list_models | No | List RunAPI models from the embedded catalog. Supports modality, service, and action filters. |
| get_model_info | No | Return service, action, modality, input constraints, and current runtime pricing for a model slug. Use service + action when a model appears in multiple endpoints. |
| list_actions | No | Group endpoint action names by modality. |
| check_pricing | No | Return current runtime pricing for a service + action + model combination. |
| search_prompts | No | Search reusable prompt examples by modality, category, tags, q, model, featured, and pagination. |
| login | No | Start browser login and save RunAPI credentials to shared local config. |
| create_task | Yes | Create a media task with a required caller-generated idempotency_key; wait for completion by default or return immediately with wait: false. |
| get_task | Yes | Fetch status and latest payload for an existing media task. |
| check_balance | Yes | Return account balance and spending metrics. |
The catalog, pricing, and prompt search tools are designed for funnel-top discovery inside coding tools.
The task and balance tools are designed for authenticated workflows.
---
Examples
Ask your assistant natural-language questions.
The assistant should use the tools to discover current model slugs and pricing instead of relying on memorized names.
Browse The Catalog
Expected behavior:
1. The assistant calls list_models with modality: "image".
2. It summarizes the returned model slugs, services, actions, and required fields.