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

How to drive Blender from OpenCode through the built-in MCP server with MCP for Blender Pro

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

  • Content
  • Advanced
  • 1 hour
  • From the README
  • Any agent

Authorization notice. MCP for Blender Pro is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Credentials. The MCP endpoint is authenticated, so keep its connection details and any provider keys out of shared files and chat logs.

Remote script. The execute_code tool runs Python inside Blender, so only let trusted clients call it and review code before it runs.

Who it is forA developer who already works in OpenCode and wants to script Blender scene operations from that client instead of the Blender panel.

The problemSwitching between an external coding client and Blender for each scene change breaks the workflow, and wiring a custom MCP connection by hand is error-prone.

The outcomeOpenCode running Blender scene tools such as scene inspection, object creation and export through the add-on's MCP server.

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 or API key for a supported provider (OpenAI, Anthropic Claude, Google Gemini, OpenRouter, OpenCode Zen, Ollama or a custom API)

Steps

  1. Install MCP for Blender Pro and keep Blender open while using an external client.
  2. Launch OpenCode Portable from the sidebar to use the Blender connection configured for you.
  3. Ask OpenCode to run get_scene_info and list_objects to confirm the connection works.
  4. For another MCP client, follow the authenticated local endpoint described in docs/CONNECTIONS.md.
  5. Check the scene in Blender after each tool call and use the undo steps if a change is wrong.

Prompt for your agent

Connect OpenCode to the mcp-for-blender-pro MCP server running inside Blender, then call get_scene_info and list_objects for <scene name>. Expected output: the scene summary and object list returned by the tools. Verify that the object count matches what is shown in Blender's outliner.

Caveat. The README says Python tool validation is not a security sandbox and external MCP clients manage their own approval policies, so review every action an external client takes.

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