Skip to content

v0.5.1 — blender_mcp bridge fix

Choose a tag to compare

@whartons whartons released this 21 Aug 01:51
· 24 commits to main since this release
567597a

Patch release: the blender_mcp bridge works again on fresh environments.

The 4309a396 pin bump gave uvx a fresh environment, which resolved blender_mcp's unbounded transitive mcp[cli] dependency to the new MCP SDK 2.x — upstream imports mcp.server.fastmcp, an SDK-1.x path that 2.x renamed, so the server died at import (MCP error -32000: Connection closed) before ever reaching Blender's socket. Old pins only appeared to work because their cached environments predated SDK 2.x.

.mcp.json now launches with uvx --with "mcp[cli]~=1.12" (≥ 1.12, < 2) — written ~= rather than <2 because the launch args transit cmd /c on Windows, where a literal < is a redirection character (#53, #54). The constraint comes off once upstream ships an SDK-2.x shim (freecad-mcp v0.1.22 already carries one and is unaffected).

Verified live post-fix: all three MCP bridges connect; Blender round-trips real scene data. Full details in the CHANGELOG.

🤖 Generated with Claude Code