MCP lands in Adobe, Blender and Unreal at SIGGRAPH

The interesting part of NVIDIA's SIGGRAPH announcements wasn't a model. It was a list of applications: Adobe Firefly and Creative Cloud, Affinity by Canva, Blender, Unreal Engine, SideFX Houdini 22, Boris FX Silhouette. All of them now speak Model Context Protocol. The tools where your product photos, video cuts, and 3D assets actually get made just grew an interface an agent can drive.

What actually happened

At SIGGRAPH 2026 in Los Angeles, NVIDIA announced MCP connections across that set of creative applications, alongside a wave of model releases.

The headline model is Cosmos 3, a world-model family shipping in three sizes: Edge at 4B parameters, Nano at 16B, and Super at 64B. Cosmos 3 Edge is available now on Hugging Face and is tuned to run in real time on Jetson, RTX PRO, DGX, and GeForce RTX hardware — meaning a 4B world model runs on a workstation you can already buy. NVIDIA also released NemoClaw, open blueprints for building custom autonomous agents, and Nemotron 3 Ultra, a 550B open model targeted at DGX Station GB300.

One more worth flagging: a Synthetic Video Detector NIM microservice, which NVIDIA says reaches up to 92% accuracy on uncompressed video. Note the qualifier. Real footage is compressed, and detection accuracy drops when it is — which is why we keep saying AI provenance tooling isn't something to govern with yet.

Why MCP in creative tools matters for your business

For a commerce operator, this is the more useful half of the announcement. Content production is where small teams bleed hours: forty product shots that need the same crop and background, a video ad in six aspect ratios, a 3D model regenerated because the SKU changed. That work has been un-automatable for most businesses because the tools were GUIs — you either clicked it yourself or paid someone to.

MCP changes the shape of that. When Blender and Creative Cloud expose the same protocol your agents already use for your CRM and your inbox, the pipeline stops being "a person in Photoshop" and starts being a workflow you can define once. Same standard, same auth story, same logging. That's the payoff of building on the protocol instead of a vendor's SDK.

Don't rebuild your studio around it this week. Do pick your single most repetitive content task — the one you've quietly accepted as the cost of doing business — and check whether that tool now has an MCP server. Then wire the boring version: one job, deterministic steps, a human looking at the output before it goes live. The gap between "we could automate that" and "we did" is usually one afternoon and a willingness to start with something small.

Sources: NVIDIA — At SIGGRAPH, NVIDIA Advances Graphics and Simulation With Agentic and Physical AI, NVIDIA at SIGGRAPH 2026.