runtime-bridge-conflict-resolver

Installation
SKILL.md

runtime-bridge-conflict-resolver

Purpose

Resolve the single-bridge constraint when more than one MCP runtime path is configured against the same Blender instance (or when ports collide). Blender accepts only one MCP bridge session per instance (default port 9876) — so running Path 1 (Official Blender Lab MCP 5.1+) and Path 2 (community mcp-for-blender, renamed from ahujasid/blender-mcp) concurrently, connecting two MCP clients to one Blender instance, colliding on port 9876, or enabling both Path 1 host (a) and host (b) on one session causes inconsistent signals.

This skill diagnoses the conflict, names the cheapest resolution, and hands off to official-runtime-readiness-checker for re-verification.

This skill is BlendOps-specific, driven by the single-bridge constraint described in docs/runtime-stack-strategy.md.

Quick start

  • list every active / configured bridge for the target Blender session
  • check for port collision (commonly localhost:9876)
  • identify which path is intended; which is residual
  • propose the cheapest disable / port-isolation step
  • hand off to official-runtime-readiness-checker to re-verify

When to use

Installs
4
GitHub Stars
4
First Seen
Jun 5, 2026