What can you do with this server?

This server gives MCP assistants scoped access to the retired Runway Aleph model line on RunAPI, mainly for querying historical tasks. * Authenticate via login, which runs a browser PKCE flow and saves the API key to ~/.config/runapi/config.json (or use RUNAPI_API_KEY). * Fetch existing tasks with get_task using a task_id (and optional action), returning status and latest result payload. * Check pricing with check_pricing, though it returns no supported model because the line is retired. * Create tasks attempted through edit_video (prompt + source video URL, with options like seed, aspect ratio, watermark, callback URL, reference image), but new requests return HTTP 410 since retirement on 2026-10-11.

How do I use @runapi.ai/runway-aleph-mcp?

1. Click on "Deploy 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., "@@runapi.ai/runway-aleph-mcp edit my video with a cinematic filter" 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.

@runapi.ai/runway-aleph-mcp

Official

by runapi-ai

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Why This Package?

@runapi.ai/runway-aleph-mcp is a focused Model Context Protocol server for the Runway Aleph model line on RunAPI. It gives MCP-compatible assistants direct access to 0 endpoints and 0 model variants without loading the full RunAPI catalog.

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

runway-aleph was retired on 2026-10-11T00:00:00Z. New requests return HTTP 410 before task creation or balance deduction. Existing tasks can still be queried. This model ID is not mapped to another model.

Related MCP server: @runapi.ai/gemini-omni-mcp

Install

Add it to Claude Code:

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

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

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

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

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

No models in this package accept new tasks. check_pricing returns no supported model. For historical task lookup, 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

Models

Runway Aleph covers 0 model variants across 0 endpoints. Each tool accepts the models listed for it:

Tool

Models

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

Agent Prompts

Query an existing task with get_task. New requests for this retired model return HTTP 410.

Check the status of my existing Runway Aleph task with RunAPI.

The assistant calls get_task with the task id and returns its status and available result.

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
Runway Aleph model page	https://runapi.ai/models/runway-aleph
npm package	@runapi.ai/runway-aleph-mcp
GitHub repository	runapi-ai/runway-aleph-mcp
RunAPI MCP overview	runapi.ai/mcp
RunAPI docs	runapi.ai/docs

License

Licensed under the Apache License, Version 2.0.

Available Tools

3 tools

check_pricingB

Look up RunAPI pricing for the runway-aleph model line.

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

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, and it says nothing about read-only safety, auth requirements, rate limits, or freshness of the pricing data. 'Look up' weakly implies a read operation, but nothing confirms it or describes the returned pricing.

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?

A single front-loaded sentence with zero waste; the resource and its scope arrive immediately.

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?

The tool is simple (two optional params, no nesting) and the schema is fully documented, so little is required. However, with no output schema the description should at least sketch what pricing information is returned (units, currency, per-call vs per-token), and it does not.

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 model slug and endpoint name are already documented as optional with sensible defaults. The description adds no syntax, format, or default-behavior detail 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.

Purpose4/5

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

States a specific verb ('look up') and resource ('RunAPI pricing') scoped to the runway-aleph model line. The unrelated siblings (get_task, login) make disambiguation unnecessary, so the only missing element is a positive statement of what it is not.

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?

Usage is only implied: an agent can infer it should call this when it needs pricing for the runway-aleph line. There is no explicit cue about when pricing is relevant, whether it can be called without auth, or what to do for other model lines.

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

get_taskB

Fetch the current status and latest result payload for a runway-aleph task.

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

B3.3/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. It does disclose the shape of the return at a high level ('current status and latest result payload'), which is useful, but says nothing about what status values exist, what the payload is before completion, auth requirements, or rate/polling limits.

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?

A single front-loaded sentence with zero filler; the verb, resource, and returned data are all in the first clause.

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?

There is no output schema, so the description is the only source for return values, and it only sketches them ('status and latest result payload'). For a simple 2-parameter read tool with full schema coverage this is adequate but leaves an agent guessing about terminal states and pre-completion payloads.

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 both parameters (task_id, action) are already documented in the schema, including the enum default behavior. The description adds no additional meaning about parameter formats or defaults; baseline 3 applies.

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

Purpose4/5

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

States a specific verb ('Fetch') and resource ('runway-aleph task'), and names the payload returned (status + latest result). It is clearly distinguishable from edit_video, check_pricing and login, though it never explicitly contrasts itself with them.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus alternatives, no polling guidance (e.g. how often to re-check a running task), and no note that a task_id must first come from edit_video. Usage is only weakly implied by the schema's 'Task id returned when the task was created'.

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.

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.

Tool Schema Changelog

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

2 tool updatesv0.3.0Oct 19, 2026
- Changedcheck_pricing1 field changed
  - removedInput schema / properties / action / enum
```
Removed value: -[
-  "edit_video"
-]
```
- Removededit_video
3 tool updatesv0.2.0Oct 5, 2026
- Changedcheck_pricing2 fields changed
  - removedInput schema / additionalProperties
```
Removed value: -false
```
  - removedInput schema / properties / model / enum
```
Removed value: -[
-  "runway-aleph"
-]
```
- Changededit_video13 fields changed
  - changedInput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```
  - addedInput schema / properties / aspect_ratio / description
```
Added value: +"Declared type: string. Known values: \"16:9\", \"9:16\", \"4:3\", \"3:4\", \"1:1\", \"21:9\"."
```
  - removedInput schema / properties / aspect_ratio / enum
```
Removed value: -[
-  "16:9",
-  "9:16",
-  "4:3",
-  "3:4",
-  "1:1",
-  "21:9"
-]
```
  - addedInput schema / properties / callback_url / description
```
Added value: +"Declared type: string."
```
  - removedInput schema / properties / model / enum
```
Removed value: -[
-  "runway-aleph"
-]
```
  - addedInput schema / properties / poll_interval_ms / maximum
```
Added value: +9007199254740991
```
  - addedInput schema / properties / prompt / description
```
Added value: +"Declared type: string."
```
  - addedInput schema / properties / reference_image_url / description
```
Added value: +"Declared type: string."
```
  - addedInput schema / properties / seed / description
```
Added value: +"Declared type: integer."
```
  - changedInput schema / properties / seed / type
```
Previous value: -"number"New value: +"integer"
```
  - addedInput schema / properties / source_video_url / description
```
Added value: +"Declared type: string."
```
  - addedInput schema / properties / timeout_ms / maximum
```
Added value: +9007199254740991
```
  - addedInput schema / properties / watermark / description
```
Added value: +"Declared type: string."
```
- Changedget_task1 field changed
  - removedInput schema / additionalProperties
```
Removed value: -false
```

3 tool updatesv0.1.7Aug 5, 2026

Changededit_video7 fields changed
- addedInput schema / properties / callback_url
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / prompt / type
```
Added value: +"string"
```
- addedInput schema / properties / reference_image_url
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / seed
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / source_video_url / type
```
Added value: +"string"
```
- addedInput schema / properties / watermark
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / required
```
Added value: +[
+  "prompt",
+  "source_video_url"
+]
```

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."

Addedlogin

3 tool updatesv0.1.0Jun 24, 2026
- First observedcheck_pricing
- First observededit_video
- First observedget_task

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.4/5.0

Scored 2026-10-19 06:45 across 3 tools

Disambiguation5/5

The three tools target clearly distinct concerns: pricing lookup, task status retrieval, and authentication. There is no plausible overlap or misselection risk between them.

Naming Consistency4/5

check_pricing and get_task follow a consistent snake_case verb_noun pattern, and login is also lowercase snake_case, though it drops the verb_noun structure. Minor deviation but overall coherent and predictable.

Tool Count3/5

Three tools is thin for a model-inference service; the surface covers auth, pricing, and status polling but feels incomplete for the apparent scope. It would be reasonable only if task submission lives in a companion server.

Completeness2/5

There is no tool to create or submit a runway-aleph task, so an agent can check pricing, authenticate, and poll a task but cannot actually start one. This is a significant lifecycle gap that would cause agent failures.

Maintenance

ActivityMaintained

ResponsivenessNo issues

Resources

Related MCP Connectors

mcp-klingOAuth
io.github.AceDataCloud
MCP server for Kling AI video generation
Image & Video Processing AI & Machine Learning
21
https://kling.mcp.acedata.cloud/mcp
mcp-wanOAuth
io.github.AceDataCloud
MCP server for Wan AI video generation
AI & Machine Learning Image & Video Processing
21
https://wan.mcp.acedata.cloud/mcp
mcp-lumaOAuth
io.github.AceDataCloud
MCP server for Luma Dream Machine AI video generation
Multimedia Processing Image & Video Processing
2
https://luma.mcp.acedata.cloud/mcp
mcp-veoOAuth
io.github.AceDataCloud
MCP server for Google Veo AI video generation
Multimedia Processing Image & Video Processing Entertainment & Media
23
https://veo.mcp.acedata.cloud/mcp

Related MCP Servers

@runapi.ai/flux-2-mcpofficial
AI & Machine Learning Image & Video Processing
runapi-ai
A
license
B
quality
B
maintenance
RunAPI MCP server for the Flux 2 model line. Create tasks, poll their status, and check pricing through a single RunAPI API key.
Updated 11 days ago (2026-10-15 09:11 UTC)
5
53 npm
Apache 2.0
@runapi.ai/gemini-omni-mcp
AI & Machine Learning Multimedia Processing
runapi-ai
A
license
A
quality
B
maintenance
MCP server for the Gemini Omni model line, enabling task creation (audio, character, text-to-video) and pricing checks through RunAPI.
Updated a month ago (2026-09-30 11:30 UTC)
6
63 npm
Apache 2.0
imagen-4-mcp
AI & Machine Learning Image & Video Processing
runapi-ai
A
license
A
quality
B
maintenance
RunAPI MCP server for the Imagen 4 model line. Create tasks, poll their status, and check pricing through a single RunAPI API key.
Updated a month ago (2026-09-30 11:34 UTC)
5
45 npm
Apache 2.0
infinitetalk-mcp
AI & Machine Learning Multimedia Processing
runapi-ai
A
license
B
quality
B
maintenance
MCP server for the InfiniteTalk model line, enabling audio-to-video task creation, status polling, and pricing checks via a RunAPI API key.
Updated a month ago (2026-09-30 11:34 UTC)
4
45 npm
1
Apache 2.0

Why This Package?

Install

Tools

Models

Agent Prompts

Configuration

Links

License

Available Tools

TDQS

TDQS

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

@runapi.ai/flux-2-mcpofficial

@runapi.ai/gemini-omni-mcp

imagen-4-mcp

infinitetalk-mcp