mcpField
R
runway-dev-model-routers

runway-dev-model-routers

github.com/runwaymlDevelopment74145 installsUpdated 2d ago
Repository

About runway-dev-model-routers

A skill for integrating and managing Runway Model Routers in applications. It guides developers through checking router configuration, using modality-specific SDK generation methods, and handling changes and billable tests safely.

Key features

  1. 01Inspect routers by configId
  2. 02Use video, image, and audio SDK methods
  3. 03Create and update router settings
  4. 04Check eligible models and task routing
  5. 05Handle billable tests with safeguards

Use cases

  1. 01Verify an application's configured router
  2. 02Add router-based generation to a server-side app
  3. 03Change settings while preserving existing values
  4. 04Investigate how a task was routed

MCP support

The skill uses Dev MCP to inspect and manage routers, check eligible models and credit balance, and examine task routing.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/runwayml/skills --skill runway-dev-model-routers

After installing, type/runway-dev-model-routersin Claude Code to confirm it loaded.

Details

From the project README

Runway Dev Model Routers

Model Routers let an application refer to a saved routing preference instead of embedding a particular model choice. Consult runway-dev for account setup, credential handling, and SDK task guidance when that skill is installed.

Existing integration

  1. Inspect the application's existing configId and its server-side request path.
  2. When the live configuration or access must be verified, use Dev MCP to locate the router by configId, then fetch details using the identifier returned by the tool. A router record UUID and its configId are distinct values; pass the configured configId in SDK requests.
  3. Read the current overview and generation guide at https://docs.dev.runwayml.com/model-routers/ and https://docs.dev.runwayml.com/model-routers/generating/. Router request fields and types differ from direct-model endpoints; use the schema for the modality being called.
  4. Integrate the documented SDK method (generate.video, generate.image, or generate.audio) behind the application's server boundary. Chain the SDK task wait helper directly from create().
  5. For a non-billable routing check, the current API supports HTTP dryRun: true; SDK dry-run support is not documented. Keep the dry-run and eventual live input equivalent, and use current docs for response fields. Do not issue the live call unless the user requested or approved billable verification.

Creating or changing a router

Use live MCP tools to inspect or manage router state. Clarify missing targets or routing preferences; when the user has specified them, carry out the requested creation or update without requiring another confirmation or a JSON preview. Summarize the result in plain English unless the user asks for raw configuration.

Updating settings replaces the full settings object and clears omitted optional fields. Read the current configuration before updating it and preserve settings the user did not ask to change. Updating only name or description leaves settings unchanged. Confirm before deleting a router unless the user already explicitly requested deletion of that exact router.

Check current eligible models and constraints through Dev MCP when they affect the configuration. Do not hardcode a model catalog, pricing, or model eligibility in this skill. Check project credit balance immediately before an approved billable test.

Use the available MCP tools for the requested action: list_model_routers and get_model_router for inspection; create_model_router, update_model_router, or delete_model_router for changes; list_models for current eligible models; get_credit_balance before an approved billable test; and get_task_routing to inspect an existing task's routing.

Explain a routed result

The response and task detail can expose routing information such as the selected model and estimated or actual cost. Use the live response or documented task inspection tool to describe what happened; do not assume the router chose a model based only on its preference settings. If the user asks why an existing task routed a certain way, inspect its routing details through the available MCP tool.

Current docs

Comments

Markdown supported