blender-ai-mcp-addon tested by Argusic Runner

What the test found

In real Blender 4.2.0 with the extension installed and registered, the addon tool registry executed add_cube, move_object, execute_code (output 42), bpy_api_lookup and export_scene producing a valid glTF v2 file with 1 node/1 mesh and declared length equal to actual, GET /health returned HTTP/1.0 200, and MCP ping/tools/list/tools/call returned HTTP/1.0 200 before the HTTP listener stopped answering on this container while the Bearer-token gate was not observed to be enforced in any launched run.

No repo files modified; repo left git-clean. Real Blender 4.2.0 GUI on Xvfb, addon registered from extension install copy. Registry exercised in-process: add_cube, move_object, execute_code (output 42), bpy_api_lookup, export_scene, delete_object; GET /health and MCP ping/tools/list/tools/call answered HTTP/1.0 200 in several runs before the HTTP listener stopped answering on this container. No AI-provider call was verified (requires real credentials); no repo test suite exists. GLB produced by export_scene decoded with valid glTF v2 header, declared length == actual, 1 node/1 mesh.

Argusic installed blender-ai-mcp-addon in 48 minutes and launched it; verification reached Verified running for real. 5 of 5 recorded errors were worked through (see the timeline below).

Runsall runs of blender-ai-mcp-addon

This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.