Skip to main content
Glama
TFMSTYLE

tfmstyle-blender-tools

by TFMSTYLE
README.md
# Blender Agent Tools

One MCP toolbox that lets any agent use the TFMSTYLE Blender addons inside a running Blender.

This is a prototype. It covers **Rock, Orbiter and Graph**. The other addons join as they pass the same test.

## The three tools

| Tool | What it does |
|---|---|
| `list_addons` | The TFMSTYLE addons running in Blender, with their versions |
| `describe_addon` | One addon's actions and settings, with current values and allowed ranges |
| `run_addon` | Applies settings, runs an action, or both |

Settings and ranges are read from Blender at the moment of the call, so nothing about any addon is kept here. Nothing is installed in Blender, and the addons themselves do not change.

`run_addon` checks everything first, and one bad value refuses the whole call. It only runs an addon's own actions. It leaves out anything that imports, exports, opens a file or goes online, and an action that clears or resets something needs `confirm=true`.

## What you need

- Blender 5.1 or newer, with the TFMSTYLE addons you want enabled, separately or through the Addon Collection
- The [MCP add-on from Blender Lab](https://www.blender.org/lab/mcp-server/), enabled with its server started
- Python 3.10 or newer

Blender Lab warns that its server runs agent written code with no guards. The checks here cover these three tools only. They do not limit what an agent can do through Blender Lab's own tools.

## Install

```bash
pip install git+https://github.com/TFMSTYLE/Blender_Agent_Tools.git
```

Then add it to your MCP client. For most clients:

```json
{
  "mcpServers": {
    "tfmstyle-blender-tools": {
      "command": "tfmstyle-blender-agent-tools"
    }
  }
}
```

It uses the same `BLENDER_MCP_HOST` and `BLENDER_MCP_PORT` settings as Blender Lab's server, and both can run at once.

## With no window

Background Blender works too, with `blender --background --online-mode --command blender_mcp`. Actions that keep running, like Orbiter's orbit, are refused there because they need an open window.

## Test

```bash
python tests/live_test.py <folder with the three zips> <collection zip>
```

It starts throwaway Blenders with their own settings folder and port, and drives them through a real MCP connection. A Blender you have open is left alone.

## License

GPL 3.0 or later.

TDQS

A3.9/5.0

Scored across 3 tools

Disambiguation5/5

Each tool targets a distinct operation: list_addons enumerates addons, describe_addon inspects one addon's actions/settings, and run_addon applies settings or executes actions. There is no meaningful overlap in purpose, and the descriptions make the boundaries clear.

Naming Consistency5/5

All three tools follow a consistent verb_noun pattern: list_addons, describe_addon, run_addon. The naming is predictable and easy to map to the intended operations.

Tool Count5/5

Three tools are well-scoped for a server focused on managing TFMSTYLE Blender addons: one to enumerate, one to inspect, and one to act. Each tool earns its place without redundancy.

Completeness4/5

The surface covers the core lifecycle of discovering addons, inspecting their settings/actions, and running them with validation and confirmation. Minor gaps exist, such as enabling/disabling addons or viewing logs, but core workflows are covered.

Maintenance

ActivityMaintained
ResponsivenessNo issues