# Blender Agent Bridge Blender Agent Bridge is a Blender extension and localhost MCP server that lets MCP-capable AI clients inspect Blender scenes, collect visual evidence, and make reversible edits. It is intended for users who want agent-assisted Blender workflows with explicit controls over trust and changes. - Findings24: - Website: - Pricing: Freemium - Categories: AI Agent Infrastructure, MCP Tools ## What is Blender Agent Bridge? Blender Agent Bridge is a Blender extension paired with a localhost MCP server. It connects Blender to external, MCP-capable AI agents so they can inspect the open scene, gather visual evidence, and assist with scene changes while keeping trust and reversibility under the user's control. The bridge is designed around scene-aware workflows rather than unrestricted automation. It provides read-only access to scene information and visual outputs, while helper edits can be reviewed through visible Commit and Revert controls. Running broader Blender Python requires an explicit session-trust setting in Blender. ## What can Blender Agent Bridge do? ### Scene-aware inspection Expose read-only information about objects, materials, animation, rigs, cameras, nodes, render settings, and \`.blend\` health to connected agents. ### Visual evidence generation Provide viewport, playblast, inspection-render, thumbnail, and render-job evidence that an agent can review before proposing or applying scene changes. ### Reversible helper edits Use helper-based editing with visible Commit and Revert controls in Blender, allowing users to review changes before making them permanent. ### Explicit script trust Keep broad Blender Python execution behind the separately enabled Trust Agent Scripts session setting rather than enabling it by default. ### Local MCP connection Run the bridge on localhost and copy a generated MCP configuration containing the local command, bridge URL, session token, version metadata, and tool-registry digest. ### Optional asset and generation workflows The repository documents provider-specific workflows involving Poly Haven, Sketchfab, Tripo, Meshy, local TripoSR, and self-hosted studio setups, with consent and provenance requirements. ## Use Cases ### Inspect an existing Blender scene Use an MCP client to examine scene structure and health across objects, materials, animation, rigs, cameras, nodes, and render settings before deciding what needs attention. ### Review a scene through generated evidence Request viewport captures, playblasts, thumbnails, or inspection renders so an agent can assess the visible result instead of relying only on scene metadata. ### Test agent-assisted edits safely Apply supported helper edits, inspect the result in Blender, and use the visible Commit or Revert controls to keep or discard the change. ### Perform deliberately trusted scripted work For workflows that require broader Blender Python access, explicitly enable session trust and run the authored operation only after accepting that higher-trust mode. ### Connect Blender to different MCP clients Start the bridge in Blender, copy its generated configuration, and connect it to Codex, Claude Desktop, Claude Code, or Cursor using the client-specific setup process. ## Frequently Asked Questions ### What does Blender Agent Bridge install? The main installation is a Blender extension that includes the MCP server in its extension ZIP. The separate MCPB package is a connector format for Claude Desktop; it does not install Blender or the Blender extension. ### What Blender version is required? The quick-start documentation requires Blender 4.2.0 or newer. The release workflow checks Blender 4.2 LTS, 4.5 LTS, and 5.1, while newer versions are allowed through capability checks rather than a fixed maximum-version gate. ### How are changes controlled? Supported helper edits are reversible and exposed through visible Commit and Revert controls in Blender. Broader Blender Python execution requires the user to explicitly enable Trust Agent Scripts for the session. ### Which AI clients are documented? The repository provides setup instructions for Codex, Claude Desktop, Claude Code, and Cursor. It describes the MCP connection as usable with other MCP-capable clients as well, but client-specific setup details may vary. ### Does the product include model-provider keys? The bridge is described as enabling agent workflows without putting a chat application or model-provider key inside Blender. Optional external asset and generation workflows have provider-specific consent and provenance requirements. ## Quick Facts - **Product type**: Blender extension and localhost MCP server - **Primary platform**: Blender 4.2.0 or newer - **Connection model**: Local bridge using MCP - **Documented clients**: Codex, Claude Desktop, Claude Code, and Cursor - **License**: GPL-3.0 - **Source**: github.com/CallMeJones/blender-agent-bridge