Return a compact, LLM-sized summary of the active scene: object names, types, transforms and visibility, plus collections, cameras, lights, the active object, the render engine and the current frame.

Use this first to see what exists. At most object_limit objects are inlined (200 by default); when objects_truncated is true, use blender.get_objects to page through the rest. No mesh data is included.

List objects with filters and a page window, for scenes too large for blender.get_scene to be useful.

type: object type to keep, e.g. "MESH", "CAMERA", "LIGHT". collection: only objects linked to this collection. name_contains: case-insensitive substring of the name. limit: page size, 1-500, default 50. offset: how many matches to skip, default 0.

Returns the page, plus "total" (matches before paging) and "truncated" (true when more objects remain) so you know whether to ask for the next page.

Return the full detail of a single object: transform, dimensions, visibility, collection, material names, modifiers, and vertex/edge/polygon counts for meshes.

Fails with OBJECT_NOT_FOUND when the name does not exist.

Create a mesh object in the active scene.

type: one of cube, sphere, cylinder, cone, plane, torus. Case does not matter. name: must be unique; an existing name fails with OBJECT_ALREADY_EXISTS rather than being renamed to "Name.001". location / scale: Blender units (meters), as [x, y, z]. rotation: DEGREES as [x, y, z], applied in XYZ Euler order.

Example: {"type": "cube", "name": "TableTop", "location": [0, 0, 1], "scale": [2, 1, 0.1]}

Change an existing object. Only the fields you pass are touched; omitted fields keep their current value.

location / scale: Blender units (meters) as [x, y, z]. rotation: DEGREES as [x, y, z]. dimensions: final bounding-box size in meters as [x, y, z] (replaces scale). visibility: hide or show the object in the viewport and renders. new_name: rename the object. Fails with OBJECT_ALREADY_EXISTS if that name is taken, rather than silently becoming "Name.001". material: material name to assign, replacing the object's material slots. Created if it does not exist yet; the response says whether it did, through "material_created". material_color: [r, g, b] or [r, g, b, a] in 0..1, used only when the material has to be created. Sets both the viewport colour and the shader, so the solid view and the render agree.

Delete an object from the active scene, checking first that it exists.

Fails with OBJECT_NOT_FOUND when the name is unknown.

Render the active scene with the current camera and return the output path and the wall-clock render time.

engine: Blender engine id, e.g. "CYCLES" or "BLENDER_EEVEE" (4.x called EEVEE "BLENDER_EEVEE_NEXT"). blender.get_scene lists the ids this Blender accepts under render.engines. Omit to keep the scene's current engine. resolution_x / resolution_y: pixels. Omit to keep the scene's render size. samples: Cycles sample count; ignored by engines without sampling. output_path: absolute or Blender-relative path. Omit to use the scene's configured output path.

Render time grows quickly with resolution and samples; prefer 512-1024 px while iterating.

Render a small preview and return the image, so you can look at what you built.

max_edge: longest edge in pixels, 64-2048, default 512. Bigger costs a lot of context, and a vision model rarely needs more to spot a mistake. engine: optional engine id; omit to keep the scene's current one. samples: optional sample count; omit for a cheap default. include_image: set false to get only the file path and no image.

Prefer this over blender.render while iterating: it is capped in size and samples and it comes back as an image. Use blender.render for a final image the user will keep.

Execute Python inside the running Blender and return whatever the snippet left in a variable named result.

code: statements to run. import bpy, import mathutils and the standard library are available. Anything that touches the network, spawns processes, reads or writes files, or reaches for eval/exec/import is rejected with VALIDATION_ERROR before Blender is contacted. Assign a JSON-serialisable value to result to get structured data back; otherwise only a summary is returned.

  Otherwise, if the server was started with ALLOW_PYTHON_EXECUTION=false,
  the call is refused with PYTHON_EXECUTION_DISABLED without contacting Blender.

Example: import bpy bpy.ops.mesh.primitive_uv_sphere_add(location=(0, 0, 1)) obj = bpy.context.object obj.name = "Ball" result = {"created": obj.name, "verts": len(obj.data.vertices)}

This tool is meant for a trusted, local AI client. It is a policy screen, not a sandbox: Blender's own API is powerful enough to do damage, and enabling this tool should be a deliberate choice.

Open a transaction. Every mutating call until commit or rollback is recorded, and blender.rollback_transaction puts all of them back.

label: optional name for the starting point, e.g. "layout". Later rollbacks can return to it by name.

Fails with TRANSACTION_ACTIVE if one is already open.

Record a named point inside the open transaction, so a later rollback can stop there instead of unwinding everything.

Use it between stages of a build: begin -> build the shell -> checkpoint "shell" -> add the details -> commit. A rollback to "shell" then discards only the details.

label: required, and unique within the transaction.

Close the open transaction and keep the changes. The undo steps stay on Blender's undo stack, so the user can still step back by hand.

Fails with TRANSACTION_NOT_ACTIVE if no transaction is open.

Put back everything the transaction changed.

to: optional checkpoint label. Omit it to rewind to the start of the transaction; name one to rewind only to that checkpoint.

Restores what the tools changed: transforms, names, visibility, materials and collection membership. Edits made through blender.execute_python are not tracked, so a transaction containing them rolls back only its tool calls.

Fails with TRANSACTION_NOT_ACTIVE if no transaction is open.

Wait until the scene changes, or until timeout seconds pass.

Use it after a change you are unsure about, instead of reading the whole scene again: it returns as soon as Blender reports a change, and tells you what changed.

timeout: seconds to wait, 0-60, default 10. objects: optional object names to narrow the answer to. Omit to watch everything. include_image: set true to also return the last render, if there is one, so a wait-and-look step is a single call.

Returns {"changed": bool, "changes": int, "waited": seconds, "changed_objects": [...]}. changed false means nothing happened before the timeout, which is an answer rather than a failure.

List the Blender instances that have connected to this server, newest first.

The active instance is the one every other tool acts on. The others are kept as history so a scene that changed unexpectedly can be explained: an entry with status "refused" or "replaced" means a second Blender tried to take the socket.

Answers even when no Blender is connected, which makes it a useful first call after a connection error.