> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pulze.io/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP server

> Point Claude, Cursor or any MCP client at Scene Manager 3 and let it read the open 3ds Max scene, make setups and render them.

The tools use the same endpoints as the [REST API](https://docs.pulze.io/scene-manager-3/developers/rest-api.md).

## Connecting a client

In Scene Manager, open **Settings > Assistants**, press **Connect** next to your client and follow the steps.

Clients connect over streamable HTTP to `http://127.0.0.1:45710/api/v1/mcp` on the same computer. No API key is needed, but Scene Manager must be open in 3ds Max.

> [tab] Claude Desktop
>
> 1. In **Settings > Assistants**, press **Connect** next to **Claude Desktop**. Claude Desktop opens with the Scene Manager extension.
> 2. Press **Install** in Claude Desktop. There is nothing else to set.
>
> If Claude Desktop does not open, drag `SceneManager.mcpb` from your Downloads folder into **Settings > Extensions** in Claude Desktop.

> [tab] Claude Code
>
> ```bash theme={null}
> claude mcp add --transport http --scope user scenemanager http://127.0.0.1:45710/api/v1/mcp
> ```
>
> Type `/mcp` in Claude Code to check that `scenemanager` is connected.

> [tab] Cursor
>
> Add this to `~/.cursor/mcp.json`:
>
> ```json theme={null}
> {
>   "mcpServers": {
>     "scenemanager": { "url": "http://127.0.0.1:45710/api/v1/mcp" }
>   }
> }
> ```

> [tab] VS Code
>
> Run **MCP: Open User Configuration** from the Command Palette and add:
>
> ```json theme={null}
> {
>   "servers": {
>     "scenemanager": { "type": "http", "url": "http://127.0.0.1:45710/api/v1/mcp" }
>   }
> }
> ```
>
> The tools are available in Copilot Chat's agent mode.

> [tab] Codex
>
> ```bash theme={null}
> codex mcp add scenemanager --url http://127.0.0.1:45710/api/v1/mcp
> ```

> [tab] Other clients
>
> A client that supports HTTP only needs the address `http://127.0.0.1:45710/api/v1/mcp`.
>
> A client that can only start a command can run the Scene Manager service in stdio mode, which forwards each message to the running Scene Manager:
>
> ```json theme={null}
> {
>   "mcpServers": {
>     "scenemanager": {
>       "command": "C:\\Program Files\\Pulze\\Scene Manager\\smsv.exe",
>       "args": ["--mcp-stdio"]
>     }
>   }
> }
> ```

Don't add Scene Manager as a **Connector** in Claude or ChatGPT. Connectors run on their servers on the internet, which can't reach your computer.

## The tools

Start with `scene_overview`: it lists everything else, with the ids the other tools need.

### Reading the scene

| | |
| - | - |
| `scene_overview` | The setups, folders, modules, quality levels and output path placeholders |
| `get_setup` | One setup as it resolves: each value and where it comes from |
| `compare_setups` | What differs between two setups, module by module |
| `find_properties` | The scene's cameras, lights, materials, layers and so on, or one object's properties |
| `selection` | What is selected in 3ds Max, or select objects there |
| `look` | A small picture of the viewport or the frame buffer |
| `missing_things` | What setups point at that the scene no longer has, and relink it |

### Setups and folders

| | |
| - | - |
| `make_setup` | A setup in one call: a copy or the scene as it is, with its name, folder, values and modules |
| `setup_from_scene` | A first setup from the scene as it is |
| `set_values` | Change values and switch modules on setups or folders |
| `activate_setup` | Apply a setup to the scene |
| `update_setup` | Rename, retag, recolor or move a setup or folder |
| `create_folder`, `delete` | Create a folder, or delete setups and folders. The scene isn't changed |
| `add_module`, `add_property`, `add_rows` | Add a module to every setup, properties to a module, objects to a table |
| `setup_thumbnail`, `setup_notes`, `setup_todos` | A setup's picture, notes and to-do list |
| `setup_brief` | A setup's prompts and camera view, for an image model |
| `create_setup` | Kept for older clients. Use `make_setup` |

### Rendering and variations

| | |
| - | - |
| `render` | Start, follow or stop a batch render of setups |
| `variation_sets`, `make_set` | List or make variation sets |
| `set_variation` | Apply one variation to the scene |
| `render_sets` | Render every variation of a set, each to its own file |
| `set_list` | Every variation of a set with its file, or as CSV |

### Comments

| | |
| - | - |
| `comments_list`, `comments_wait` | Find comments asked of the assistant, or wait for new ones |
| `comment_read` | One comment with its shot, pin and context |
| `comment_create` | Pin a comment on a shot of the viewport or the frame buffer |
| `comment_take`, `comment_reply`, `comment_resolve` | Take a comment, reply with what changed, and mark it done for a person to review |

### Anything else

| | |
| - | - |
| `run_script` | Run MaxScript or Python in 3ds Max |

Scene Manager doesn't create materials, lights or maps. It turns what is already in the scene into setups.

## Worth trying

> [accordion] Which setups are there, and which are missing an output path?
>
> `scene_overview`, then `get_setup` on the ones that look incomplete.

> [accordion] Make a dusk version of every kitchen setup.
>
> `make_setup` with `copyOf` for each, and the sun's time changed in `values`. `compare_setups` checks that only the sun changed.

> [accordion] Render the Exterior folder at Draft quality.
>
> `scene_overview` with the folder as `filter`, then `render` with those setups and `quality: "Draft"`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.