Authorization notice. Blender AI MCP Addon is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Who it is forA technical artist taking over an unfamiliar Blender file who needs to understand its layout before editing it.
The problemAn inherited scene with many objects, parents and materials is hard to understand quickly, and edits made too early can break it.
The outcomeA plain explanation of the scene's object structure from the assistant, with no changes made to the file.
What you need first
- Blender 4.2 or later (the release bundle targets Windows x64)
- The mcp-for-blender-pro.zip file from the Releases page
- An account and API key or connection details for at least one supported provider (OpenAI, Anthropic Claude, Google Gemini, OpenRouter, OpenCode Zen, Ollama or a custom API)
- Blender kept open while using Studio or an external client
Steps
- Install and enable mcp-for-blender-pro as described in the Install and create section of the README.
- Open 3D Viewport → N → MCP Pro and select a provider and model.
- Open the scene you want to review in Blender.
- Send this message: Inspect this scene and explain its object structure before making any changes.
- Read the explanation and the list of objects, then decide which edits to request in a separate message.
Prompt for your agent
Using the mcp-for-blender-pro repo, ask the Blender assistant to inspect the open scene and explain its object structure without changing anything. Return the object hierarchy and material list, and verify that get_scene_info and list_objects were the tools used.
Caveat. The README says Python tool validation is not a security sandbox, so review any file before relying on the assistant's reading of it.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page