Blender MCP · Client setup

Setting up your MCP client

Synthetic Setup does all of this for you. This page shows what it adds to each client, in case you prefer to edit the config by hand: the entry, where it goes per client, and how to check that Blender responds.

1. The entry for your client

Install with Synthetic Setup first: it adds this entry to Claude Desktop, Cursor, Claude Code and Codex with your license, and leaves the server on your computer. To edit a client by hand, the command is node with the path to the server that Synthetic Setup left in your user folder, and your license in BLENDER_MCP_LICENSE (if Synthetic Setup added Node.js for you, keep the command it wrote instead of node). Replace your-license-key with your real key from /dashboard/licenses and YOUR_USER with your user name on that computer.

{
  "mcpServers": {
    "blender": {
      "command": "node",
      "args": ["C:\\Users\\YOUR_USER\\.synthetic\\launchers\\blender-mcp\\launcher.mjs"],
      "env": {
        "BLENDER_MCP_LICENSE": "your-license-key",
        "NODE_USE_SYSTEM_CA": "1"
      }
    }
  }
}

2. Where it goes per client

Claude Desktop

Edit %APPDATA%\Claude\claude_desktop_config.json. Drop the block into the mcpServers object. If you already have other servers, add it as one more key.

Cursor

Settings → Cursor Settings → MCP → Edit Config. Paste the snippet into the JSON and save.

Codex CLI / Other

The file ~/.codex/config.toml uses TOML format. Convert the snippet — example:

[mcp_servers.blender]
command = "node"
args = ['C:\Users\YOUR_USER\.synthetic\launchers\blender-mcp\launcher.mjs']
env = { BLENDER_MCP_LICENSE = "your-license-key", NODE_USE_SYSTEM_CA = "1" }

3. Restart the client and try it

Quit the MCP client and reopen it — servers are loaded at startup. Then open Blender with the add-on enabled (see the install guide) and ask the client something like:

If it answers with your objects, the connection works. If not, see the troubleshooting guide.