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 product designer or small studio artist who needs a quick display mockup for a client review.
The problemSetting up a basic product stage by hand means many repeated steps for primitives, lights, camera and materials.
The outcomeA simple product-display scene with a pedestal, camera, three lights and a matte blue material, checked in the viewport preview.
What you need first
- Blender 4.2 or later; the release bundle targets Windows x64
- The mcp-for-blender-pro.zip file from the GitHub Releases page
- An account and API key for a supported provider (OpenAI, Anthropic Claude, Google Gemini, OpenRouter, OpenCode Zen), or a local Ollama install, or a compatible custom endpoint
- Service keys for Poly Haven, Sketchfab or Poly Pizza if you want asset search and import
Steps
- Install and enable mcp-for-blender-pro in Blender, then open 3D Viewport, N, MCP Pro.
- Select a provider and model that support tool calling.
- Open Studio Window to see the chat, scene objects and viewport snapshots side by side.
- Send this message: Create a simple product-display scene with a pedestal, a camera and three lights. Give the pedestal a matte blue material.
- Check the viewport preview, then ask for corrections in the same conversation.
Prompt for your agent
Using the mcp-for-blender-pro add-on in Blender, build a product-display scene with a pedestal, one camera and three lights using the add_cube, add_cylinder, add_camera, add_light and set_material tools. Return the list of created object names. Verify with viewport_screenshot that the pedestal has the matte blue material.
Caveat. Results depend on the model you pick, so use a model with tool-calling support and expect to refine the output.
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