Runway demonstrates a Fable 5.2 electronic-flute workflow inside Claude

• Runway demonstrated a playable electronic-flute project inside Claude using Fable 5.2, according to its announcement.
• The workflow moves from Runway concepts to a Blender prototype, then back to Runway for textures and renders, as shown in the demo thread.
• Access runs through Runway MCP, the connection layer linked in Runway’s setup post.

A moka-pot photo becomes a multi-scene coffee commercial, with one kitchen and consistent lighting, in Runway’s MCP examples. Connecting the service uses a Runway account login rather than an API key.

The Blender handoff is the interesting bit. Runway’s demonstration assigns each stage a distinct job:

1. Runway: create concepts for the electronic flute.
2. Blender: develop the prototype.
3. Runway: produce the final textures and renders.

The company also posted a separate, eight-second quick demo:

Runway publishes its generation endpoint on the MCP server page. Its Claude connection guide documents this setup for personal accounts:

1. Open Claude on the web or desktop, then Customize → Connectors → Add.
2. Enter Runway as the name and https://mcp.runwayml.com/mcp as the URL.
3. Select Continue, then Connect, and sign in to Runway.

Claude Team and Enterprise workspaces require an administrator to add the connector first.

Every generation through MCP uses Runway credits, according to the billing FAQ. Unlimited Mode and Explore Mode do not apply, including for operations such as upscaling that may be covered inside the Runway app.

• Retries and regenerations: each counts as a separate, charged generation.
• Cost: varies with the model, resolution and other settings.
• Approval: the host app decides when to invoke Runway. The guide describes asking the assistant to obtain approval before starting a generation.