QUADIFY
By Anvil Interactive Solutions
← Home

Connecting AI Clients

BlenderMCP Pro's server speaks the standard MCP HTTP transport, so any MCP-compatible client can connect to it. The Client dropdown in the main panel handles the common cases automatically.

Claude Desktop

Select Claude Desktop from the Client dropdown and click Write Claude Desktop Config. BlenderMCP Pro locates your claude_desktop_config.json automatically:

  • Windows — %APPDATA%\Claude\claude_desktop_config.json
  • macOS — ~/Library/Application Support/Claude/claude_desktop_config.json
  • Linux — ~/.config/Claude/claude_desktop_config.json

It writes an mcpServers entry pointing at http://127.0.0.1:7842/mcp using the HTTP transport. Restart Claude Desktop after connecting for the new server to be picked up.

Cursor

Select Cursor and click Write Cursor Config. This writes to ~/.cursor/mcp.json with the same server entry. Restart Cursor to load it.

Windsurf

Select Windsurf and click Write Windsurf Config. This writes to ~/.codeium/windsurf/mcp_config.json. Restart Windsurf to load it.

Claude.ai (Web)

Since Claude.ai runs in the cloud, it can't reach 127.0.0.1 on your machine directly — it needs a public tunnel URL pointed at your local server. Select Claude.ai (Web) from the Client dropdown and click Start Tunnel.

This requires cloudflared or ngrok to be installed and available on your system PATH. Once the tunnel is up, BlenderMCP Pro displays the public URL in the panel — click Copy Tunnel URL and add it as a custom connector in Claude.ai's settings. Click Stop Tunnel when you're done; leaving a tunnel running exposes your local Blender session to that URL for as long as it's active, so only keep it open while you're actively using it.

Manual / Other Clients

For any other MCP-aware client or your own integration, select Manual. The panel displays the local endpoint directly:

http://127.0.0.1:7842/mcp

Click Copy URL and paste it into whatever client or script you're wiring up, using the standard MCP HTTP transport.

Verifying the Connection

Once a client is connected and issues its first tool call, it appears in the "Recent Tool Calls" list on the main panel with a timestamp, the tool name, a success/failure icon, and execution time in milliseconds. This is the fastest way to confirm a client is actually talking to Blender.

If a Client Won't Connect

  • Confirm the server shows "Running" in the main panel before writing any client config — configs written while stopped will fail on first use.
  • Always fully restart the client application (not just reload a window) after writing its config file.
  • For Claude.ai, confirm cloudflared or ngrok is actually installed and on PATH — the panel will show "Requires cloudflared or ngrok in PATH" if it can't find either.
  • If you changed the port in Preferences, reconnect the client — previously written configs point at the old port.