Headless Blender asset QA over MCP: background script runs and FBX reimport verification.
This MCP server provides headless Blender asset QA over MCP. A background script runs to perform FBX reimport verification, enabling automated checking of Blender assets during reimport workflows. The server is focused on validating that FBX inputs round-trip correctly via Blender without interactive use.
🛠️ Key Features
MCP-based interface for asset QA
Headless Blender operation
Background script execution
FBX reimport verification
🚀 Use Cases
Verifying Blender asset correctness after FBX reimport
Automating QA steps in asset pipelines that use Blender
⚡ Developer Benefits
Programmatic access to Blender QA tasks via MCP
Suitable for non-interactive validation in tooling and workflows
⚠️ Limitations
Described scope is limited to FBX reimport verification and asset QA
No additional tools, topics, or operational details are provided
An asset-QA tool for game and 3D asset pipelines: verify that an exported FBX actually reimports cleanly in headless Blender — mesh count, material count, and required naming prefixes checked automatically, with a deterministic JSON result instead of a manual eyeball pass. blender_verify_fbx_reimport is the core tool; blender_locate and blender_run_script are the general-purpose primitives it is built on.
No add-on. No TCP port. No background daemon. This server does not install anything into Blender, does not open a socket for a running Blender instance to connect to, and does not keep Blender resident. Each call spawns blender --background --python <script.py>, waits for a bounded, timeout-guarded exit, and returns the result — headless and stateless by design. It does not download assets and does not collect telemetry.
How this differs from other Blender MCP servers. Most Blender MCP projects (e.g. ahujasid/blender-mcp, the official Blender Labs MCP server) drive a live, running Blender GUI over a TCP/add-on bridge for interactive scene editing — a different use case with a different trust model (an open socket, an installed add-on, a persistent process). This server instead targets CI-style, one-shot asset verification: run it in a pipeline step, get a pass/fail JSON, move on. If you need live GUI control, use a reviewed Blender MCP add-on separately (see Safety below).
NOTE
AI / LLM Integration & Machine-Readable Context: AI assistants (Claude, Codex, Gemini) can read llms.txt for machine-readable context, search phrases, and tool documentation. Regression test suites guard privacy hygiene and runtime memory safety.
Tools
Tool
Purpose
blender_verify_fbx_reimport
Generate a temporary Blender verification script, import an FBX, and write a JSON result with mesh/material counts and missing required prefixes.
blender_run_script
Run blender --background --python <script.py> with optional arguments and bounded stdout tail.
blender_locate
Resolve the Blender executable from an explicit path, BLENDER_EXE, the verified local default, or PATH.
Safety
This server runs local Python inside Blender. Use only scripts and asset paths you trust.
The default timeout is bounded.
No remote asset marketplaces, API keys, or telemetry are included.
For live GUI control, use a reviewed Blender MCP add-on separately.
BLENDER_EXE — optional path to the Blender executable. Without it, tools try the explicit blenderPath argument, then BLENDER_EXE, then a verified local Windows default, then PATH.
Every tool also accepts an explicit blenderPath argument per call, which takes priority over BLENDER_EXE.
Process output is retained only as a tail: blender_run_script defaults to 8,000 characters (configurable up to 50,000); FBX verification keeps 8,000. The response marks outputTruncated: true when earlier output was discarded, so verbose Blender scripts cannot grow the MCP process memory without bound.
Testing framework for LLM operating systems (7 dimensions)
Desktop Software
Our partner organization open-bricks bundles AI-native desktop applications — a modern, open-source software suite built for the age of AI. Categories include file management, document tools, developer utilities, and more.
