blendersessiond Star on GitHub

Local Blender orchestration

Blender Sessions.
Under agent control

blendersessiond launches, configures, owns, checks, and stops isolated local GUI Blender Sessions for agent workflows.

  • Cross-platform
  • Loopback-only
  • Named Sessions
  • MCP ready
Get started View on GitHub
A local controller routing one agent connection to three isolated Blender sessions.

Quickstart

Up in seconds.

Install, start a named Session, and call Blender—locally.

session/demo 
$ git clone https://github.com/BramVR/blendersessiond.git$ uv tool install ./blendersessiond$ blendersessiond doctor$ blendersessiond start --name demo✓ Session "demo" started (PID 42421) on 127.0.0.1:51842$ blendersessiond call get_scene_info --name demo{  "name": "(Unsaved)",  "objects": 3,  "active_object": "Cube"}
macOS 12+ Windows 10+ Linux glibc 2.28+ Python 3.11+ Status All systems healthy

Built for agents

Everything your Blender agent needs

A focused CLI + MCP bridge for reliable, scriptable Blender control on your local machine.

Explore all features

Own the lifecycle

Doctor, start, inspect, save, and stop Sessions with confidence.

Isolated & repeatable

Each Session runs independently with its own state, logs, and port.

Loopback-only

Binds to 127.0.0.1. No remote control plane. No surprises.

Named Sessions

Run multiple Sessions side by side and target each by name.

MCP ready

Connect agents to Blender through the Model Context Protocol.

Session lifecycle

A lifecycle you can script.

blendersessiond doctor ready to host a Session

MCP integration

Wire Blender
into your agent.

One static client command resolves the healthy Session and its dynamic loopback port at runtime.

MCP documentation
.mcp.jsonproject root
{
  "mcpServers": {
    "blender": {
      "command": "blendersessiond",
      "args": ["mcp-serve"]
    }
  }
}

Local by design

Secure by default.
Private by choice.

Loopback-only

Addon APIs bind to 127.0.0.1 with no external exposure.

No telemetry

Zero usage tracking. The daemon only records local Session state.

Your data stays local

.blend files and scene data never leave your machine.

Operator notes

Know the boundaries.

The essential facts about how blendersessiond runs, connects, and protects your Blender Sessions.

4 verified facts

What does blendersessiond do?

It launches, owns, checks, and stops isolated local GUI Blender Sessions so scripts and AI agents can control Blender predictably.

lifecycle

Can an AI agent control Blender through MCP?

Yes. mcp-serve connects an MCP client to one healthy named Session and resolves its dynamic loopback port at runtime.

MCP

Does Blender data leave the machine?

No. Addon APIs bind to 127.0.0.1; Session state, logs, scene data, and .blend files stay local.

local only

Does blendersessiond run Blender headlessly?

No. It is designed for same-machine GUI Blender Sessions and does not provide a remote control plane or headless mode.

GUI Session

Ready when your agent is

Ready to automate Blender?

Give your local agent a Blender Session it can trust.

Get started View on GitHub