Headless Blender asset QA over MCP: background script runs and FBX reimport verification.
Headless Blender asset QA over MCP: background script runs and FBX reimport verification. The ellmos blender use mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 3 defined tools rather than through you.
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.
Everything the assistant can do here goes through one of these:
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 prefixesblender_run_script — Run blender --background --python <script.py> with optional arguments and bounded stdout tailblender_locate — Resolve the Blender executable from an explicit path, BLENDER_EXE, the verified local default, or PATHBeing a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Ellmos Blender Use's toolset — blender_verify_fbx_reimport, blender_run_script, blender_locate — is a fair guide to whether it matches your workflow. It is maintained by ellmos-ai; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| 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. |
{
"mcpServers": {
"blender-use": {
"command": "node",
"args": ["<path-to-repo>/src/index.js"]
}
}
}Configuration as documented by the project. Restart the client after saving.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.