Blender SLOP

Blender SLOP is a native Blender add-on that exposes Blender as a SLOP provider. It uses BlenderMCP as reference material for useful scene-control behaviors, but it does not run an MCP server, call a BlenderMCP socket, or depend on BlenderMCP internally.

The add-on runs inside Blender, imports the published slop-ai Python SDK, and serves SLOP over WebSocket.

What It Exposes

• SLOP server status and connection URL.
• Scene summary, timeline, render settings, world settings, collections, object count, materials, selected objects, active object, cameras, and lights.
• Object nodes with transform, visibility, selection, dimensions, modifiers, material state, camera data, and light data.
• Object affordances for inspect, select, rename, duplicate, visibility, transform, set material, add/apply modifier, keyframe transform, and delete.
• Scene affordances for viewport capture, still render, render settings, frame/range control, world color, and arbitrary Blender Python execution.
• Collection affordances for mesh primitive creation, file import, camera creation, light creation, collection creation, object moves, and material creation.

Install

For local development outside Blender:

uv sync --extra dev
uv run pytest

Blender Setup

1. Open Blender.

2. Install the addon/blender_slop_addon folder as a Blender add-on. To make an installable zip:

   cd addon
   zip -r ../blender_slop_addon.zip blender_slop_addon

   Then use Edit > Preferences > Add-ons > Install....

3. Enable Interface: Blender SLOP.

4. In the 3D View sidebar, open the Blender SLOP tab.

5. Click Install Dependencies once to install slop-ai[websocket] into Blender's Python environment.

6. Restart Blender or disable and re-enable the add-on if Blender cannot import the dependency immediately.

7. Click Start SLOP Provider.

By default the provider listens on:

ws://127.0.0.1:8765/slop

State Shape

The root provider id is blender. The main app node is:

/blender/workspace

Useful paths include:

/blender/workspace/scene
/blender/workspace/scene/objects
/blender/workspace/scene/cameras
/blender/workspace/scene/lights
/blender/workspace/scene/collections
/blender/workspace/scene/timeline
/blender/workspace/scene/render
/blender/workspace/scene/world
/blender/workspace/materials
/blender/workspace/server
/blender/workspace/last_result

All actions are SLOP affordances attached to the node they operate on. Dangerous actions such as execute_python, object transforms, material edits, primitive creation, importing, rendering, modifier application, keyframing, and deletion are marked dangerous.

Coverage

BlenderMCP covers a compact tool surface: scene/object inspection, viewport screenshots, arbitrary code execution, and optional external asset/generation services for Poly Haven, Sketchfab, Hyper3D Rodin, and Hunyuan3D. Blender SLOP now covers those core Blender controls natively and adds first-class SLOP nodes for the major Blender work areas an AI needs for day-to-day scene work: objects, materials, cameras, lights, collections, timeline/animation, render settings, viewport capture, still rendering, file import, modifiers, and world settings.

The external asset/generation services are not bundled as native provider features yet. They can still be reached through execute_python if the user has their own scripts or add-ons installed, and they are good candidates for future optional SLOP integration nodes.

Security Notes

This provider can run arbitrary Python inside Blender because it intentionally exposes that SLOP affordance. Treat SLOP consumers as untrusted, review dangerous affordances before invocation, and save Blender work before running destructive scene operations.

Attribution

BlenderMCP was used as reference material and is MIT licensed. This repository does not vendor BlenderMCP code. See NOTICE.