What can you do with this server?

This server enables AI agents to create and manage Seedance text-to-video tasks via RunAPI, with three core capabilities: * text_to_video: Generate videos from text prompts using Seedance models (seedance-1.5-pro, seedance-2.0, seedance-2.0-fast, seedance-v1-lite, seedance-v1-pro, seedance-v1-pro-fast). Configure aspect ratio (1:1, 4:3, 16:9, 9:16, etc.), duration (4–12 seconds), and output resolution (480p, 720p, 1080p). Optionally provide source images, reference audio/video, or first/last frame images. Can poll until completion and return output URLs, or return immediately with a task ID. * get_task: Fetch the current status and result payload for an existing Seedance task using its task ID. * check_pricing: Retrieve a current pricing snapshot for any Seedance model and endpoint — no API key required.

How do I use seedance-mcp?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@seedance-mcp generate a video of a cat playing piano using seedance-2.0" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

seedance-mcp

by runapi-ai

Overview Schema Source Related Servers Score Discussions Admin

TypeScript

Remote

Why This Package?

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

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

Related MCP server: seedream-mcp

Install

Add it to Claude Code:

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

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

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

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

{
  "mcpServers": {
    "seedance": {
      "command": "npx",
      "args": ["-y", "@runapi.ai/seedance-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

Tool	Auth	Purpose
`text_to_video`	Yes	Create a Seedance text to video task and optionally wait for a terminal status. Returns the task id, status, and output URLs.
`get_task`	Yes	Fetch the current status and latest payload for an existing task.
`check_pricing`	No	Look up current pricing for a Seedance model and endpoint.

Models

Seedance covers 7 model variants across 1 endpoint. Each tool accepts the models listed for it:

Tool	Models
`text_to_video`	`seedance-1.5-pro`, `seedance-2-mini`, `seedance-2.0`, `seedance-2.0-fast`, `seedance-2.5`, `seedance-v1-pro`, `seedance-v1-pro-fast`

Model availability can change between releases. Use check_pricing or the Seedance 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

Run a Seedance text to video task with RunAPI.

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

Submit without waiting

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

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

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

Configuration

The server resolves auth in this order:

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

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

{
  "apiKey": "your_runapi_key"
}

Do not commit real API keys.

Links

Resource	URL
Seedance model page	https://runapi.ai/models/seedance
npm package	@runapi.ai/seedance-mcp
GitHub repository	runapi-ai/seedance-mcp
RunAPI MCP overview	runapi.ai/mcp
RunAPI docs	runapi.ai/docs

License

Licensed under the Apache License, Version 2.0.

Available Tools

4 tools

check_pricingA

Look up RunAPI pricing for the seedance model line.

ParametersJSON Schema

Name	Required	Description	Default
`model`	No	Model slug. Defaults to the line's primary model.
`action`	No	Endpoint name. Defaults to the endpoint that offers the model.

TDQS

A3.8/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden of behavioral disclosure. 'Look up' implies a read-only operation, but the description does not explicitly state side effects, response behavior, authentication needs, or error cases. It is minimally transparent but not richly detailed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no filler or redundant information. Every word contributes to the tool's purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity and fully documented parameters, the description is mostly complete. However, there is no output schema and the description does not explicitly state what the returned pricing information looks like, which is a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the input schema already documents both parameters with enums and defaults. The description adds no additional parameter meaning beyond naming the model line, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Look up') and resource ('RunAPI pricing for the seedance model line'), clearly distinguishing this tool from siblings like text_to_video, get_task, and login. It precisely identifies what the tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool should be used when pricing information for seedance models is needed, but it provides no explicit guidance about when to prefer it over alternatives or any exclusions. It is adequate but lacks direct usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_taskA

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

ParametersJSON Schema

Name	Required	Description	Default
`action`	No	Asynchronous endpoint the task was created on. Defaults to the line's only asynchronous endpoint.
`task_id`	Yes	Task id returned when the task was created.

TDQS

A3.5/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must fully disclose behavior. It states it fetches status and payload, but does not mention read-only nature, error behavior for missing tasks, or any side effects. This is insufficient for a simple fetch tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence with no redundant information. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description vaguely mentions 'status and latest result payload' but lacks detail on return format or structure. For a fetch tool, more specificity about the response would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (both parameters described), so the description adds no extra meaning beyond what the schema already provides. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb 'Fetch' and clearly names the resource 'seedance task', and the purpose is distinct from sibling tools (login, text_to_video, check_pricing).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage after task creation but does not explicitly state when to use it versus alternatives like text_to_video or what conditions are required. No exclusions or prerequisites are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

loginA

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

ParametersJSON Schema

Name	Required	Description	Default
`force`	No	Re-run browser login when the current credential comes from the local config file.

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the behavioral burden. It discloses the interactive browser flow and the file write side effect (config.json). However, it does not mention that it may overwrite existing credentials or that it could block waiting for user input, though these are implied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, well-structured sentence that front-loads the action ('Authenticate RunAPI') and provides necessary details without extraneous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple login tool with one optional parameter and no output schema, the description covers the core purpose and side effect. It lacks an explicit statement that this is a prerequisite for other tools, but that is implied.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% (the only parameter 'force' has a description). The tool description adds no additional meaning about parameters beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('Authenticate'), target resource ('RunAPI'), method ('browser PKCE login flow'), and side effect (saving to config.json). It is distinct from sibling tools, none of which relate to authentication.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage (to authenticate RunAPI) but does not explicitly say when to run it (e.g., before other RunAPI tools) or when to use the 'force' parameter. Since there are no alternative auth tools among siblings, 'vs alternatives' is not applicable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

text_to_videoB

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

ParametersJSON Schema

Name	Required	Description
`seed`	No
`wait`	No	Poll until the task reaches a terminal status.
`model`	No	RunAPI model slug for this model line.
`prompt`	No
`timeout_ms`	No
`web_search`	No
`lock_camera`	No
`aspect_ratio`	No
`callback_url`	No
`output_format`	No	Output video container format.
`generate_audio`	No
`duration_seconds`	No
`poll_interval_ms`	No
`output_resolution`	No
`return_last_frame`	No	Whether to return the generated video's last frame.
`source_image_urls`	No
`last_frame_image_url`	No
`reference_audio_urls`	No
`reference_image_urls`	No
`reference_video_urls`	No
`enable_safety_checker`	No
`first_frame_image_url`	No

TDQS

B3.1/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool returns a task id, status, and output URLs, but omits critical behavioral traits: whether the operation is synchronous or asynchronous (wait parameter suggests polling), potential for long execution, authentication requirements, rate limits, or failure modes. The agent is left with insufficient transparency for a task-creation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no waste, and the action is front-loaded. It is concise, but for a tool with 22 parameters, the brevity borders on under-specification. It earns its place but does not leverage the available sentence to add value beyond the one-line purpose. Score 4 for appropriate conciseness without penalizing the lack of detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the high complexity (22 parameters), absence of output schema, and zero annotations, the description is severely inadequate. It only states the return type but does not explain parameter constraints, default behaviors, or edge cases. An agent cannot correctly invoke this tool without external knowledge, making the description functionally incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 18%, meaning 82% of parameters lack any explanation. The description does not compensate for this: it fails to explain any parameter semantics, such as the meaning of wait, seed, aspect_ratio, or the many reference inputs. It only provides high-level context ('text to video') without mapping to specific parameters, leaving the agent to guess the purpose of most fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the action (Create a Seedance task), the resource (RunAPI), and the domain (text to video). It distinguishes itself from sibling tools (login, get_task, check_pricing) by stating a unique verb and resource. The purpose is specific and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for text-to-video generation but provides no explicit guidance on when to use this tool versus alternatives. It does not mention exclusions or conditions, and the lack of a direct comparison to siblings leaves the agent to infer applicability. No misleading guidance, but also no helpful routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

1 tool updatev0.2.0Aug 27, 2026

Changedtext_to_video12 fields changed

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / aspect_ratio / anyOf

Added value: +[
+  {
+    "const": "1:1",
+    "type": "string"
+  },
+  {
+    "const": "4:3",
+    "type": "string"
+  },
+  {
+    "const": "3:4",
+    "type": "string"
+  },
+  {
+    "const": "16:9",
+    "type": "string"
+  },
+  {
+    "const": "9:16",
+    "type": "string"
+  },
+  {
+    "const": "21:9",
+    "type": "string"
+  },
+  {
+    "const": "auto",
+    "type": "string"
+  }
+]

removedInput schema / properties / aspect_ratio / enum

Removed value: -[
-  "1:1",
-  "4:3",
-  "3:4",
-  "16:9",
-  "9:16",
-  "21:9",
-  "auto"
-]

removedInput schema / properties / aspect_ratio / type
```
Removed value: -"string"
```

addedInput schema / properties / output_format / anyOf

Added value: +[
+  {
+    "const": "mp4",
+    "type": "string"
+  },
+  {
+    "const": "mov",
+    "type": "string"
+  }
+]

removedInput schema / properties / output_format / enum
```
Removed value: -[
-  "mp4",
-  "mov"
-]
```
removedInput schema / properties / output_format / type
```
Removed value: -"string"
```

addedInput schema / properties / output_resolution / anyOf

Added value: +[
+  {
+    "const": "480p",
+    "type": "string"
+  },
+  {
+    "const": "720p",
+    "type": "string"
+  },
+  {
+    "const": "1080p",
+    "type": "string"
+  },
+  {
+    "const": "4k",
+    "type": "string"
+  }
+]

removedInput schema / properties / output_resolution / enum

Removed value: -[
-  "480p",
-  "720p",
-  "1080p",
-  "4k"
-]

removedInput schema / properties / output_resolution / type
```
Removed value: -"string"
```
addedInput schema / properties / poll_interval_ms / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / timeout_ms / maximum
```
Added value: +9007199254740991
```

2 tool updatesv0.1.12Aug 19, 2026

Changedcheck_pricing1 field changed

changedInput schema / properties / model / enum

Previous value: -[
-  "seedance-1.5-pro",
-  "seedance-2-mini",
-  "seedance-2.0",
-  "seedance-2.0-fast",
-  "seedance-v1-pro",
-  "seedance-v1-pro-fast"
-]New value: +[
+  "seedance-1.5-pro",
+  "seedance-2-mini",
+  "seedance-2.0",
+  "seedance-2.0-fast",
+  "seedance-2.5",
+  "seedance-v1-pro",
+  "seedance-v1-pro-fast"
+]

Changedtext_to_video3 fields changed

changedInput schema / properties / model / enum

Previous value: -[
-  "seedance-1.5-pro",
-  "seedance-2-mini",
-  "seedance-2.0",
-  "seedance-2.0-fast",
-  "seedance-v1-pro",
-  "seedance-v1-pro-fast"
-]New value: +[
+  "seedance-1.5-pro",
+  "seedance-2-mini",
+  "seedance-2.0",
+  "seedance-2.0-fast",
+  "seedance-2.5",
+  "seedance-v1-pro",
+  "seedance-v1-pro-fast"
+]

addedInput schema / properties / output_format

Added value: +{
+  "description": "Output video container format.",
+  "enum": [
+    "mp4",
+    "mov"
+  ],
+  "type": "string"
+}

addedInput schema / properties / return_last_frame

Added value: +{
+  "description": "Whether to return the generated video's last frame.",
+  "type": "boolean"
+}

2 tool updatesv0.1.11Aug 5, 2026

Changedcheck_pricing1 field changed

changedInput schema / properties / model / enum

Previous value: -[
-  "seedance-1.5-pro",
-  "seedance-2-mini",
-  "seedance-2.0",
-  "seedance-2.0-fast",
-  "seedance-v1-lite",
-  "seedance-v1-pro",
-  "seedance-v1-pro-fast"
-]New value: +[
+  "seedance-1.5-pro",
+  "seedance-2-mini",
+  "seedance-2.0",
+  "seedance-2.0-fast",
+  "seedance-v1-pro",
+  "seedance-v1-pro-fast"
+]

Changedtext_to_video2 fields changed

changedInput schema / properties / aspect_ratio / enum

Previous value: -[
-  "1:1",
-  "4:3",
-  "3:4",
-  "16:9",
-  "9:16",
-  "21:9",
-  "auto",
-  "9:21"
-]New value: +[
+  "1:1",
+  "4:3",
+  "3:4",
+  "16:9",
+  "9:16",
+  "21:9",
+  "auto"
+]

changedInput schema / properties / model / enum

Previous value: -[
-  "seedance-1.5-pro",
-  "seedance-2-mini",
-  "seedance-2.0",
-  "seedance-2.0-fast",
-  "seedance-v1-lite",
-  "seedance-v1-pro",
-  "seedance-v1-pro-fast"
-]New value: +[
+  "seedance-1.5-pro",
+  "seedance-2-mini",
+  "seedance-2.0",
+  "seedance-2.0-fast",
+  "seedance-v1-pro",
+  "seedance-v1-pro-fast"
+]

2 tool updatesv0.1.9Jul 22, 2026

Changedget_task1 field changed

changedInput schema / properties / action / description

Previous value: -"Endpoint the task was created on. Defaults to the line's only endpoint."New value: +"Asynchronous endpoint the task was created on. Defaults to the line's only asynchronous endpoint."

Changedtext_to_video2 fields changed
- addedInput schema / properties / seed / maximum
```
Added value: +2147483647
```
- addedInput schema / properties / seed / minimum
```
Added value: +-1
```

3 tool updatesv0.1.7Jul 11, 2026

Changedcheck_pricing1 field changed

changedInput schema / properties / model / enum

Previous value: -[
-  "seedance-1.5-pro",
-  "seedance-2.0",
-  "seedance-2.0-fast",
-  "seedance-v1-lite",
-  "seedance-v1-pro",
-  "seedance-v1-pro-fast"
-]New value: +[
+  "seedance-1.5-pro",
+  "seedance-2-mini",
+  "seedance-2.0",
+  "seedance-2.0-fast",
+  "seedance-v1-lite",
+  "seedance-v1-pro",
+  "seedance-v1-pro-fast"
+]

Addedlogin
Changedtext_to_video19 fields changed
- addedInput schema / properties / callback_url
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / enable_safety_checker
```
Added value: +{
+  "type": "boolean"
+}
```
- addedInput schema / properties / first_frame_image_url / type
```
Added value: +"string"
```
- addedInput schema / properties / generate_audio
```
Added value: +{
+  "type": "boolean"
+}
```
- addedInput schema / properties / last_frame_image_url / type
```
Added value: +"string"
```
- addedInput schema / properties / lock_camera
```
Added value: +{
+  "type": "boolean"
+}
```
- changedInput schema / properties / model / enum
```
Previous value: -[
-  "seedance-1.5-pro",
-  "seedance-2.0",
-  "seedance-2.0-fast",
-  "seedance-v1-lite",
-  "seedance-v1-pro",
-  "seedance-v1-pro-fast"
-]New value: +[
+  "seedance-1.5-pro",
+  "seedance-2-mini",
+  "seedance-2.0",
+  "seedance-2.0-fast",
+  "seedance-v1-lite",
+  "seedance-v1-pro",
+  "seedance-v1-pro-fast"
+]
```
- changedInput schema / properties / output_resolution / enum
```
Previous value: -[
-  "480p",
-  "720p",
-  "1080p"
-]New value: +[
+  "480p",
+  "720p",
+  "1080p",
+  "4k"
+]
```
- addedInput schema / properties / prompt
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / reference_audio_urls / items
```
Added value: +{}
```
- addedInput schema / properties / reference_audio_urls / type
```
Added value: +"array"
```
- addedInput schema / properties / reference_image_urls / items
```
Added value: +{}
```
- addedInput schema / properties / reference_image_urls / type
```
Added value: +"array"
```
- addedInput schema / properties / reference_video_urls / items
```
Added value: +{}
```
- addedInput schema / properties / reference_video_urls / type
```
Added value: +"array"
```
- addedInput schema / properties / seed
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / source_image_urls / items
```
Added value: +{}
```
- addedInput schema / properties / source_image_urls / type
```
Added value: +"array"
```
- addedInput schema / properties / web_search
```
Added value: +{
+  "type": "boolean"
+}
```

1 tool updatev0.1.4Jun 24, 2026
- Changedtext_to_video3 fields changed
  - addedInput schema / properties / duration_seconds / maximum
```
Added value: +12
```
  - addedInput schema / properties / duration_seconds / minimum
```
Added value: +4
```
  - addedInput schema / properties / duration_seconds / type
```
Added value: +"number"
```
3 tool updatesv0.1.0Jun 24, 2026
- First observedcheck_pricing
- First observedget_task
- First observedtext_to_video

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.7/5.0

Scored 2026-08-27 01:25 across 4 tools

Disambiguation5/5

Each tool serves a clearly distinct purpose: authentication, task creation, status retrieval, and pricing lookup. There is no overlap or ambiguity between them.

Naming Consistency4/5

Tool names follow a consistent snake_case pattern with verb-first or noun-verb structure (login, get_task, check_pricing). text_to_video deviates slightly as a noun phrase, but it remains predictable and readable, so minor inconsistency only.

Tool Count5/5

Four tools is well-scoped for a text-to-video generation server. Each tool is necessary for the core workflow (auth, create, fetch status) plus pricing, without redundancy or bloat.

Completeness4/5

The core lifecycle of text-to-video is covered: authentication, task creation, and status polling. Missing cancel or list operations, but these are not essential for the primary use case, and pricing adds value. Minor gap only.

Maintenance

ActivityNo data

ResponsivenessNo issues

Resources

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

runapi-mcpOAuth
io.github.runapi-builder
130+ AI models for image, video, music, and audio — 18 model families, one RunAPI account.
AI & Machine Learning Multimedia Processing
155
MusevateOAuth
com.musevate
Text, image and reference-to-video across many AI video models. Musevate account required.
AI & Machine Learning Image & Video Processing
1
mcp A
com.unifically
One API for 100+ AI video, image, music and speech models.
AI & Machine Learning Image & Video Processing Audio Processing
141
Future Video Studio A
video.future
Create and manage cinematic AI video renders through the Future Video Studio Agent API.
AI & Machine Learning Image & Video Processing
82

Related MCP Servers

kling-mcp
AI & Machine Learning Image & Video Processing
runapi-ai
A
license
B
quality
A
maintenance
Enables interaction with Kling AI models for video generation and avatar tasks via RunAPI, including task creation, status polling, and pricing checks.
Updated a month ago (2026-07-31 09:32 UTC)
8
46
Apache 2.0
seedream-mcp
Image & Video Processing AI & Machine Learning
runapi-ai
A
license
B
quality
A
maintenance
Enables creating, polling, and checking pricing for Seedream image generation tasks (edit and text-to-image) through a single RunAPI API key.
Updated a month ago (2026-08-12 05:19 UTC)
6
73
Apache 2.0
grok-imagine-mcp
AI & Machine Learning Image & Video Processing
runapi-ai
A
license
B
quality
A
maintenance
Enables AI image and video generation tasks (text-to-image, image-to-video, edit, upscale, etc.) via RunAPI, with support for polling and pricing lookups.
Updated 7 days ago (2026-09-04 10:59 UTC)
10
280
Apache 2.0
@runapi.ai/happyhorse-mcpofficial
AI & Machine Learning Multimedia Processing Image & Video Processing
runapi-ai
A
license
A
quality
A
maintenance
Enables creating and managing HappyHorse video generation tasks (edit, image-to-video, text-to-video) via RunAPI, with optional polling for completion and pricing lookup.
Updated a month ago (2026-07-31 09:34 UTC)
6
69
Apache 2.0

Why This Package?

Install

Tools

Models

Agent Prompts

Create a task

Submit without waiting

Check pricing before creating

Configuration

Links

License

Available Tools

Tool Schema Changelog

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

@runapi.ai/happyhorse-mcpofficial