scene-save

Scene / Save

Save Opened scene to the asset file. Use 'scene-list-opened' tool to get the list of all opened scenes.

Inputs

• openedSceneName (optional) — name of an opened scene to save. Empty/null = active scene.
• path (optional) — destination .unity path. Empty/null = save back to the scene's existing path.

Validation

Throws if the scene cannot be resolved, has no existing path AND no override path was supplied, or the supplied path does not end with .unity. On EditorSceneManager.SaveScene failure, surfaces an error with the current opened-scenes list for diagnosis.

How to Call

unity-mcp-cli run-tool scene-save --input '{
  "openedSceneName": "string_value",
  "path": "string_value"
}'

> For complex input (multi-line strings, code), save the JSON to a file and use:

> ```bash

> unity-mcp-cli run-tool scene-save --input-file args.json

> ```

>

> Or pipe via stdin (recommended):

> ```bash

> unity-mcp-cli run-tool scene-save --input-file - <<'EOF'

> {"param": "value"}

> EOF

> ```

Troubleshooting

If unity-mcp-cli is not found, either install it globally (npm install -g unity-mcp-cli) or use npx unity-mcp-cli instead.

Read the /unity-initial-setup skill for detailed installation instructions.

Input

| Name | Type | Required | Description |

|------|------|----------|-------------|

| openedSceneName | string | No | Name of the opened scene that should be saved. Could be empty if need to save the current active scene. |

| path | string | No | Path to the scene file. Should end with ".unity". If null or empty save to the existed scene asset file. |

Input JSON Schema

{
  "type": "object",
  "properties": {
    "openedSceneName": {
      "type": "string"
    },
    "path": {
      "type": "string"
    }
  }
}

Output

This tool does not return structured output.