How to connect Runway to OpenClaw
Connect Runway to OpenClaw with ClawLink: paste your Runway key once and 22 tools work from chat. No MCP server to run, nothing stored on your machine.
RunwayAPI KEYMCPRunway provides generative AI APIs for creating and transforming video, images, audio, avatars, voices, and media workflows.. Once connected, OpenClaw can read and act on Runway from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Runway access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Runway setup: install one ClawHub skill, connect Runway in the browser, and OpenClaw can call real Runway actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to Runway.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Runway
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Runway?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Runway in the ClawLink dashboard — paste your Runway API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Runway, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Runway is connected in the dashboard, that agent calls the same 22 Runway tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Runway MCP for OpenClaw
Looking for a Runway MCP server for OpenClaw? ClawLink connects Runway to OpenClaw and exposes 22 Runway tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Runway integration works the same way.
What the OpenClaw Runway integration can do
22 Runway tools are ready for OpenClaw once the account is connected. The 21 below are the ones people reach for most; your agent can call all 22.
21 of 22 Runway tools for OpenClaw
| Tool | What it does |
|---|---|
Get document runway_get_document | Get one Runway knowledge document, including its full content and the avatars that currently |
Get organization runway_get_organization | Return the connected Runway organization's credit balance, monthly credit spend cap, exact |
Get task runway_get_task | Get the current status, cost, output URLs, and failure details for a Runway generation task |
Get usage runway_get_usage | Return daily Runway credit usage by model for an optional UTC date range of up to 90 days |
Get workflow runway_get_workflow | Get a published Runway workflow version and its graph so node IDs and output keys can be |
Get workflow invocation runway_get_workflow_invocation | Get the current status, completed node output URLs, and node or invocation failure details for |
List documents runway_list_documents | List Runway knowledge documents one page at a time, with sorting and an opaque continuation |
List workflows runway_list_workflows | List the connected account's published Runway workflows and their available versions, ordered |
Create document runway_create_document | Create a Runway knowledge document from markdown or plain text for reuse by avatar workflows |
Create ephemeral upload runway_create_ephemeral_upload | Create only a temporary Runway media upload slot and return its presigned multipart form |
Generate image runway_generate_image | Start a Runway text-to-image or reference-guided image generation task and return its task ID |
Generate sound effect runway_generate_sound_effect | Generate an audio effect from a text prompt and return the task ID and estimated credit cost |
Generate speech runway_generate_speech | Synthesize speech with Runway using an exact model-specific voice and option contract, then |
Generate video from image runway_generate_video_from_image | Animate one or more input images with a selected Runway model and return the task ID and |
Generate video from text runway_generate_video_from_text | Start a Runway text-to-video task with a model-specific typed request and return its task ID |
Run workflow runway_run_workflow | Invoke a published Runway workflow, optionally overriding graph node outputs, and return the |
Transform video runway_transform_video | Transform or restyle an existing video with Runway and return the created task ID and estimated |
Update document runway_update_document | Change the name, content, or both for an existing Runway knowledge document |
Upscale image runway_upscale_image | Start a Runway image upscaling task and return its task ID and estimated credit cost |
Upscale video runway_upscale_video | Start a Runway video upscaling task and return its task ID and estimated credit cost |
Cancel task runway_cancel_task | Cancel a running Runway task or delete its task record |
Try it: find the Runway tool you need
Browse the 21 Runway tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Runway, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Runway, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Runway, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Runway, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Runway working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Runway API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Runway account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Runway. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Runway actions to the runtime in a format your agent can reliably use. | 22 tools for Runway are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Runway to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Runway in the browser, and the 22 tools above work from chat. There is no SDK and no config file, and the Runway key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Runway skill but can't call the tools
The ClawHub skill teaches OpenClaw about Runway, but the calls run through the ClawLink plugin and your connected account. Make sure Runway is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Runway from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Runway tools
Runway tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Runway call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Runway returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Runway has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Runway integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Runway: link your Runway account once in the browser and OpenClaw can call the Runway API through 22 ready-made tools — no custom code or token handling.
How do I add Runway to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Runway skill from ClawHub, then you click Connect in the dashboard to authorize Runway. OpenClaw calls the tools from the next message — no config files, and the Runway key you paste is stored server-side instead of in your environment.
How long does it take to connect Runway to OpenClaw?
About two minutes. Sign in, click Connect next to Runway in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Runway up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Runway working from chat.
OpenClaw installed the Runway skill but can't call the tools
The ClawHub skill teaches OpenClaw about Runway, but the calls run through the ClawLink plugin and your connected account. Make sure Runway is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Related
DataRobot
DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets.
OpenClaw Chatbotkit integration
ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications.
Just One API tools
Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.