Skip to main content
Scene Manager 3 is in beta. Routes, operation names and tools may change before release.
Everything Scene Manager 3 does goes through the Scene Manager service, which runs on your computer next to 3ds Max. The Scene Manager UI uses it, and your scripts and AI assistants can use it the same way: to manage setups and folders, change modules, run batch renders, build variations and work with comments.

How Scene Manager thinks

  • A setup is a saved state of the scene: its camera, lighting, resolution, output and so on.
  • A setup’s values are grouped into modules. When a module is off, that part of the scene is left alone.
  • Setups can be organized into folders, and a folder’s values apply to every setup inside it.
  • Activating a setup writes its values into the open scene. A batch render activates and renders each setup in turn.
Scene Manager doesn’t create anything in your scene. It works with what is already there and switches between saved states of it.

Three ways in

REST API

Everything Scene Manager can do. The other two are built on it.

Python SDK

No dependencies, so it also runs inside 3ds Max’s own Python.

MCP server

Let Claude, Cursor or another assistant work on the open scene.
An operation has the same name everywhere: GET /setups is listSetups in the API reference and scene.setups.list_setups() in Python.

What the API covers

The API reference lists every endpoint by area.