Use this for first use and connection failures. Call blender_connection_status before asking the
user to repeat setup. If it is not connected, call blender_getting_started and present its actual
Blender discovery result, official download URL, Add-on name, steps, and bundled screenshots.
Use this user-facing summary:
Don't have Blender yet? Download the installer
Open Blender, enable the MCP add-on in Preferences > Add-ons, then click Start MCP Server in the N panel.
Clarify that the trusted Add-on name is Blender Connector and its N-panel category is Codex. A separately installed community Add-on named MCP for Blender is not the endpoint for this plugin and must not be treated as proof that the Blender Harness is connected.
Use the screenshots and steps returned by blender_getting_started; do not depend on package-level
documents that disappear in granular installs. Do not install Blender, enable Add-ons, or change MCP
configuration without the user's authorization. Never request or display the private Harness
descriptor token.
For error-specific recovery, supported/unsupported boundaries, common misrouting patterns, and first-use examples, follow the workflow and recovery table below; granular installs must not rely on package-level files that may be absent.
When to Use
Use for first-time connections, or when Blender is not installed, the add-on is not enabled, the server is not started, the port is unreachable, or the session cannot be discovered.
Prerequisites
- First obtain the current connection status and the actual Blender probe result, and do not make the user repeat completed steps.
- Distinguish the official Blender Connector from the community MCP for Blender; do not request private tokens.
Workflow
Step 1. Call blender_connection_status and classify by failure level.
Step 2. When not connected, call blender_getting_started, showing its actual path, official URL, steps, and screenshots.
Step 3. Confirm Blender, the add-on, the N panel button, and the local endpoint item by item; do not automatically install or change configuration.
Step 4. After connecting, re-probe and perform a read-only scene check to prove the Harness session is usable.
Validation
Record the CLI/add-on version, Blender path, add-on name, connection status, session discovery, and read-only check results; for tokens, report only their existence and do not echo their values.
Rules and Capability Boundaries (Not Applicable Scenarios)
Without authorization, do not download or install, do not enable the add-on, do not edit the MCP configuration, and do not treat a community add-on or an occupied port as a trusted Harness connection.
Gotchas (Common Issues and Recovery)
- Wrong add-on found: point out the name difference and switch according to the local instructions.
- Service started but unreachable: check the listening address, process, and firewall; do not require disclosure of the token.
- Incompatible version: report the detected version and the supported range, and stop speculative fixes.