DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to control Blender from an external MCP client with Blender AI MCP Addon

Connect an MCP client to Blender's authenticated local endpoint and run scene tools from it.

  • Content
  • Advanced
  • 45 minutes
  • From the README
  • Any agent

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.

Remote script. The execute_code tool runs Python inside Blender, and the README says Python tool validation is not a security sandbox, so only connect clients you trust.

Who it is forA developer or technical artist who wants to script Blender from an AI tool they already use.

The problemManually switching between a coding tool and Blender for repeated scene operations breaks the flow of work.

The outcomeAn external MCP client that lists the Blender tools and runs scene operations through the local endpoint.

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

  1. Install and enable mcp-for-blender-pro in Blender and keep Blender open.
  2. Open the connection guide at docs/CONNECTIONS.md to get the local endpoint and its authentication details.
  3. Launch OpenCode Portable from the sidebar, or add the endpoint to your MCP client using the connection guide.
  4. Ask the client to list the available Blender tools, then run a read-only call such as get_scene_info.
  5. Confirm the result appears in Blender before running any editing tool.

Prompt for your agent

Connect to the authenticated local Streamable HTTP MCP endpoint of the mcp-for-blender-pro add-on, following docs/CONNECTIONS.md. Call get_scene_info on <target .blend file> and return the scene summary. Verify the call succeeds with Blender open and that no object changed.

Caveat. External MCP clients manage their own approval policies, so the built-in approval prompts in Blender may not apply to them.

Share: 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