Blender Ai MCP Server

Blender Ai MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Blender Ai MCP directly instead of describing what you should do. blender-ai-mcp lets Claude, ChatGPT, Codex, and other MCP clients control Blender through a stable tool API instead of ad-hoc Python generation. The result is a safer, smaller, and more reliable surface for real modeling work: goal-first.

What the assistant can call

Once Blender Ai MCP is connected, these are the calls the assistant has available:

• Goal — first orchestration.** Normal guided sessions start from router_set_goal(...), so the system knows what the model is trying to build before it starts
• Truth — first verification.** Inspection, measurement, and assertion tools determine what is actually true in Blender
• router_set_goal — router_get_status
• browse_workflows — reference_images
• scene_scope_graph — scene_relation_graph
• scene_view_diagnostics — search_tools
• call_tool — optional prompt bridge tools when MCP_PROMPTS_AS_TOOLS_ENABLED=true:
• list_prompts — get_prompt
• scene_get_viewport — scene_clean_scene
• build — phase cleanup is still allowed when recovery is needed
• Ready-to — paste local MCP client config examples for guided/manual surfaces plus MLX, OpenRouter, and Gemini vision variants
• Research — driven upgrade proposal for scene graphs, symbolic relation notation, and supporting geometry-library choices

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Choosing this one

Plenty of developer tooling 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. Blender Ai MCP's toolset — Goal, Truth, router_set_goal and 11 more — is a fair guide to whether it matches your workflow. It is maintained by patrykiti; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Blender Ai MCP.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the blender ai mcp mcp server does with a few real requests.