1. Home
  2. BlenderMCP
  3. BlenderMCP for VS Code: Setup & Config

Data as of

BlenderMCP for VS Code: Setup & Config

BlenderMCP links VS Code to Blender for scene inspection, object and material changes, and Python execution.

BlenderMCP VS Code configuration

  1. Choose VS Code configuration scope

    For BlenderMCP, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

  2. Add BlenderMCP to VS Code

    Use the blender-mcp entry below in servers. Keep BlenderMCP's documented stdio connection fields and your other VS Code entries.

  3. Check BlenderMCP in VS Code

    BlenderMCP: Start in VS Code’s MCP controls; inspect output and trust prompts.

Config file · Workspace: .vscode/mcp.json

JSON
{
  "servers": {
    "blender-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "blender-mcp"
      ],
      "env": {}
    }
  }
}

BlenderMCP in VS Code: stdio checks

  • Make uvx blender-mcp (from uv, for Python tools) available in the workspace, container, or remote environment hosting BlenderMCP. Start through VS Code's MCP controls; inspect output and trust prompts.
  • BlenderMCP uses stdio here: VS Code must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
Tools
get_scene_info, get_object_info, get_viewport_screenshot

BlenderMCP — details. VS Code guide

Frequently asked questions

For BlenderMCP, edit workspace .vscode/mcp.json. VS Code requires servers rather than mcpServers; preserve the displayed type on each entry.

VS Code's blender-mcp example uses stdio.

BlenderMCP's VS Code configuration invokes uvx blender-mcp (from uv, for Python tools).

BlenderMCP's stored list contains 17 tools, including get_scene_info, get_object_info, get_viewport_screenshot. Compare those names with VS Code's connected tool list; the stored list is not a live check.