How to connect Runway to Hermes Agent (paste one key, 22 tools)

Most guides for giving Hermes Agent Runway access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Runway setup: pair once in the browser and your always-on Hermes agent can act on Runway for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.

Setup

It takes three steps to connect Hermes to Runway.

1
Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
2
Connect Runway
Paste your API key in the dashboard.
3
Use it from chat
Ask Hermes Agent: "What can you do with Runway?"

Install by command

The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:

hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin    # prints an approval link — open it and approve
hermes clawlink finish   # after approving in the browser
hermes clawlink test

Then connect Runway in the ClawLink dashboard — paste your Runway API key once.

Verify the connection by asking Hermes:

Pull the relevant data from Runway, summarize it in plain English, and point out anything that needs attention.

Using a different agent?

The Hermes 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 login

login 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 Hermes

Looking for a Runway MCP server for Hermes Agent? ClawLink connects Runway to Hermes Agent and exposes 22 Runway tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Runway integration works the same way.

What the Hermes Agent Runway integration can do

22 Runway tools are ready for Hermes Agent 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 Hermes

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

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 Hermes Agent. 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 Hermes Agent 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

Hermes paired but still can't use Runway

Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.

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 Hermes Agent Runway integration?

Yes. ClawLink is the fastest way to connect Hermes to Runway: link your Runway account once in the browser and Hermes Agent can call the Runway API through 22 ready-made tools — no custom code or token handling.

How do I connect Runway to Hermes with ClawLink?

Install the plugin with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pair once: run hermes clawlink begin, approve the link in your browser, and run hermes clawlink finish. Connect Runway in the dashboard and Hermes can use it 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 Hermes Agent?

About two minutes. Sign in, click Connect next to Runway in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

Why use ClawLink instead of wiring Runway up myself?

Hermes paired but still can't use Runway

How to connect Runway to Hermes Agent

Setup

Install and pair

Connect Runway

Use it from chat