What problem does it solve?
Claude MCP plugin changes fail silently: a wrong UNIFI_MCP_HTTP_FORCE flag or an asyncio.wait(FIRST_COMPLETED) pattern makes all tools disappear without errors, and Bash 4 syntax breaks setup scripts on macOS without clear messages. This Skill provides the procedures to configure, verify, and release the unifi-network, unifi-protect, and unifi-access plugins without hitting these failure modes.
Core Features & Use Cases
- Transport Stability: Enforces the stdio-primary asyncio pattern in transport.py so HTTP bind failures never cancel the stdio task and silently remove tools.
- Plugin Configuration: Sets UNIFI_MCP_HTTP_FORCE correctly across all three plugin.json files and distinguishes --plugin-dir local development from marketplace cache behavior.
- Setup Verification & Portability: Runs check-prereqs.sh before activation and keeps shell scripts compatible with Bash 3.2 on stock macOS.
- Release Discipline: Issues no-op patch releases when only plugin.json changes, keeping plugin versions slaved to PyPI package tags.
- Use Case: After editing plugins/unifi-network/plugin.json, grep all three plugins for the flag, test scripts with /bin/bash, run check-prereqs.sh, then cut a no-op patch release so marketplace users receive the fix.
Quick Start
Audit the three plugin.json files for UNIFI_MCP_HTTP_FORCE and verify transport.py uses the stdio-primary pattern before my next plugin release.