v0.1.3

Renames the add-on's user-visible strings to match the project, and documents the design-rule tools and the Claude Desktop setup that actually works. No changes to the server, tools or design rules themselves.

uvx blender-mcp-bridge serve

Installing blender-mcp-bridge moves you from 0.1.2 to 0.1.3.

Changed

• The add-on still registered under the pre-rename name. Blender listed it as Blender MCP for n8n and its sidebar tab read Blender MCP (n8n), so a fresh install showed a name that no longer matched the project. It now registers as Blender MCP Bridge under a Blender MCP tab. The same stale name is gone from the README heading, the package docstring, the serve banner and the Studio footer.

  n8n remains a supported client. The references that document real behaviour — the schema-default stripping for n8n's MCP client, the socket backlog sizing, the stateless-client sections — are unchanged.

  Reload the add-on in Blender to pick up the new panel; this restarts its socket server.

Documentation

• The three design-rule tools are now documented. check_design, get_design_rules and list_design_topics answer from a local JSON export with no LLM, no embedding model and no print-kb checkout — a lookup returns in milliseconds. The README now says so, names the tools, and gives the prompt pattern that gets them consulted before geometry is generated rather than after.

  It also records two things that are easy to get wrong: value_source separates numbers stated in a cited source from conventional FDM defaults, and check_mesh_for_printing verifies that a mesh is manifold — which is not the same as verifying that two parts fit.

• Claude Desktop needs the mcp-remote shim. A direct {"type": "streamable-http", "url": "..."} entry is rejected at startup with "Some MCP servers could not be loaded … were skipped", so the documented config now spawns mcp-remote instead. The README also notes that Claude Desktop reads its config only at launch, that closing the window is not quitting, and that Settings → Connectors → Add custom connector is a dead end for a local server: that path sends the URL to Anthropic's cloud, which then dials the server itself, so it requires public HTTPS and rejects http://127.0.0.1.

• The CLI is invoked by its console script throughout. The sessions and troubleshooting sections spelled every command as uv run python -m blender_mcp_bridge.main …, which read like the only way in while the Quick Start already used the short form. uv run blender-mcp-bridge … from a checkout, blender-mcp-bridge … from an install.

Fixed

• uv could write its cache into the project root. With UV_CACHE_DIR pointing at the repo, uv sync scattered sdists-v*/, wheels-v*/, interpreter-v*/ and CACHEDIR.TAG across the working tree. A uv.toml now pins the cache directory, and .gitignore covers the bucket names for the case where a shell's stale environment variable overrides it.

Requirements

Python 3.10+ and Blender 5.0 with the bundled add-on.

Links

• PyPI
• Full changelog

v0.1.2

Fixes the release workflow, which could not run its own test suite. No changes to the server, tools or design rules.

uvx blender-mcp-bridge serve

v0.1.1 was tagged but never reached PyPI — its publish run failed before upload — so this release supersedes it. Installing blender-mcp-bridge moves you from 0.1.0 to 0.1.2.

Fixed

• pytest was never a declared dependency. The publish workflow's test step failed with Failed to spawn: pytest, because the dev dependency group listed only ruff and mypy. Local runs had masked this: uv run pytest silently fetches an ephemeral copy, so the suite passed on a developer machine and failed on a clean CI checkout. pytest>=8.0 is now declared, and uv.lock updated to match.

Requirements

Python 3.10+ and Blender 5.0 with the bundled add-on.

Links

• PyPI
• Full changelog

v0.1.1

Maintenance release. No changes to the server, tools or design rules — v0.1.0 remains functionally current.

uvx blender-mcp-bridge serve

Fixed

• CI ran against a directory that no longer exists. The ruff, McCabe and mypy jobs still pointed at src/, left over from the rename to blender_mcp_bridge/, so every run failed on a missing path rather than on the code.
• The dependency audit could not install its own requirements. uv export emitted the project itself as an editable -e .; because every other line carries --hash, pip ran in hash-checking mode and refused an install with no single file to hash. Exporting with --no-emit-project drops the self-reference.
• Broken print-kb links. docs/design-rules.md and the bundled print-design-rules skill linked to ../../print-kb, a sibling-directory path that only resolved on a local checkout. Both now point at seehiong/print-kb.

Added

• Publishing to PyPI on release. Publishing a GitHub Release now builds and uploads the package via Trusted Publishing, with no API token stored anywhere.
• Two release guards. The workflow fails early if the tag and the pyproject.toml version disagree, or if the design-rules copy bundled into the wheel is out of step with the export — the latter having nearly shipped a stale 111-rule snapshot in v0.1.0.

Requirements

Python 3.10+ and Blender 5.0 with the bundled add-on.

Links

• PyPI
• Full changelog

v0.1.0

First release on PyPI.

uvx blender-mcp-bridge serve

An MCP server that gives AI agents hands-on control of Blender — modelling, materials, rendering, and 3D-print design checks.

What's in it

• 98 MCP tools across modelling, materials, lighting, rendering, sculpting, scene management and print preparation.
• 259 3D-printing design rules from 25 sources, covering tolerances, overhangs, wall thickness, orientation, supports and bed adhesion. Bundled in the wheel, so an installed package answers a design question with no repo checked out.
• Blender Studio — a visual session editor with an AI Assistant panel.
• Session playback — record a modelling session as JSON and replay it deterministically.
• Community projects — cable comb and stackable bin, both built from the design rules and printed.

Requirements

Python 3.10+ and Blender 5.0 with the bundled add-on.

Links

• PyPI
• Design rules documentation