- Runware MCP Server
Runware MCP Server
Visit https://runware.ai/mcp for more details
What is Runware MCP Server?
Runware MCP Server is a Model Context Protocol server that connects AI agents to Runware's full model catalog, image, video, audio, 3D, and text/LLM models from every major provider, plus thousands of community models. It exposes tools for generating and editing media, searching the catalog, and checking pricing, so any MCP-compatible client can run Runware tasks directly from a conversation.
How to use Runware MCP Server?
To use Runware MCP Server, add a custom connector in Claude Desktop pointing to the hosted server at https://mcp.runware.ai and sign in with your Runware account via OAuth. Alternatively, configure it locally within the mcpServers section of your claude_desktop_config.json file, running npx -y @runware/mcp with your Runware API key set as an environment variable.
Key features of Runware MCP Server?
- Run any Runware task, including image, video, audio, 3D, and text/LLM generation, plus upscaling, background removal, and model training, through a single run tool.
- Chain models across modalities in one request, for example turning an image into a video, adding generated audio, and appending a voiceover, without leaving the agent.
- Browse and filter the model catalog by capability, category, or creator, and pull curated examples and pricing before running a task.
- Fetch a model's JSON Schema to validate parameters, and look up the status of a previously submitted task by its UUID.
Use cases of Runware MCP Server
- Generating a full asset set, stills and clips, inside a coding agent session without switching to a separate tool.
- Running media generation as a step in an automation or pipeline.
- Previewing a model's sample outputs before picking one, or reproducing and tweaking a past generation.
FAQ
Can I use Runware MCP Server with other apps?
Yes! It works with any MCP-compatible client, including Claude & Claude Desktop, Cursor, Codex, VS Code, and Windsurf
Who pays for generations made through the MCP server?
Your Runware API key carries your account identity, so usage is billed to your Runware balance at standard rates. There is no MCP-specific surcharge.
Server Config
{
"mcpServers": {
"runware": {
"command": "npx",
"args": [
"-y",
"@runware/mcp"
],
"env": {
"RUNWARE_API_KEY": "<YOUR_RUNWARE_API_KEY>"
}
}
}
}