Luma MCP

First, a quick disambiguation: this page is about the Luma Dream Machine video model, not the lu.ma events app that shares the name. Luma shipped its own official MCP server, so an agent can point at Luma and call Luma's own models. That is the right tool when Luma's models are exactly what you need. It is also single vendor and self-hosted: the server exposes one roster, and your agent is wired to it alone.

Wireflow takes the opposite shape. It is a hosted node canvas where you assemble a video workflow, then publish it. Publishing turns that graph into a REST endpoint and an MCP tool in the same step, so an agent can pick the best hosted model per shot instead of one vendor's stack. Route a hero shot to Luma Dream Machine and a background plate to another model inside a single AI video workflow, and keep one endpoint while the models underneath rotate.

The mechanism is worth understanding, because it is where the multi-model advantage comes from. You build a workflow on the canvas: a text input, a video model node such as Luma Dream Machine or Veo 3.1, and optionally an upscale step. When you publish it, Wireflow registers it on a hosted MCP server and as a REST endpoint at the same time. Nothing is deployed by you, and there is no local server to keep alive.

An agent connected to that server sees the workflow as a tool with typed inputs. It calls the tool, gets an execution id, polls until the run finishes, and reads back the asset URLs. Because the tool is your graph, not a single model, you can swap Luma Dream Machine for Kling underneath without changing the call. That is the same contract behind a video creation and editing API: one stable tool, many models, typed in and typed out.

If your product depends on Luma's specific models or the tooling built around them, use Luma's own official MCP server; those models live there, and no canvas layer changes that. Wireflow does not host Runway, Pika, or Midjourney models, and it will never claim to. It is also not the reasoning brain: it generates and returns media, it does not write your strategy or decide your shot list for you.

Wireflow earns its place when the job is bigger than one fixed vendor: when you want to pick the best model per shot, chain generation into upscaling, keep one endpoint while models rotate underneath it, or hand the whole pipeline to an agent as an MCP tool. If you want a Sora-style model in the same graph as Luma Dream Machine, compare the hosted Sora video model alternative and open the flow to inspect the graph.