1. Home
  2. BlenderMCP
  3. BlenderMCP for Cursor: Setup & Config

Data as of

BlenderMCP for Cursor: Setup & Config

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

BlenderMCP Cursor configuration

  1. Choose Cursor configuration scope

    For BlenderMCP, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

  2. Add BlenderMCP to Cursor

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

  3. Check BlenderMCP in Cursor

    BlenderMCP: Enable in Cursor’s MCP settings; inspect tools.

Config file · Project: .cursor/mcp.json

User: ~/.cursor/mcp.json

JSON
{
  "mcpServers": {
    "blender-mcp": {
      "command": "uvx",
      "args": [
        "blender-mcp"
      ],
      "env": {}
    }
  }
}

BlenderMCP in Cursor: stdio checks

  • Cursor must find uvx blender-mcp (from uv, for Python tools) for BlenderMCP. Enable the project/user entry in MCP settings and inspect its tools.
  • BlenderMCP uses stdio here: Cursor 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. Cursor guide

Frequently asked questions

Cursor's BlenderMCP entry belongs under mcpServers in .cursor/mcp.json (project) or ~/.cursor/mcp.json (user). Confirm the active scope in MCP settings.

Cursor's blender-mcp example uses stdio.

BlenderMCP's Cursor 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 Cursor's connected tool list; the stored list is not a live check.