UniFi MCP goes multi-server: Protect, Access, shared packages, and Claude Code plugins

[sirkirby]

We've been busy. Here's everything that landed this week:

Three MCP Servers

UniFi MCP is now a monorepo with three independent MCP servers:

Server	Tools	Status	Package
Network	91	Stable	unifi-network-mcp
Protect	34	Beta	unifi-protect-mcp
Access	29	Beta	unifi-access-mcp

Protect covers cameras, smart detections (person/vehicle/animal/package), NVR health, recordings, RTSP streams, snapshots, lights, sensors, and chimes. Real-time event streaming via websocket buffer.

Access covers door lock/unlock, NFC/PIN/mobile credentials, visitor passes, access policies, schedules, and event history. Dual authentication (API key for reads, proxy session for mutations).

Both are on PyPI and Docker, same install experience as Network.

Shared Packages

~2,500 lines of duplicated code across the servers were extracted into two shared packages:

• unifi-core — auth strategies, connection management, controller detection, retry policies
• unifi-mcp-shared — permissions, confirmation flow, lazy tool loading, meta-tools, config

This ensures all three servers behave identically: same permission model, same preview-then-confirm flow, same lazy loading. Adding a fourth server (Drive is planned) means importing the shared packages and focusing only on domain logic.

Claude Code Plugin Marketplace

The fastest way to get started is now the plugin marketplace:

/plugin marketplace add sirkirby/unifi-mcp
/plugin install unifi-network@unifi-plugins
/unifi-network:setup

Each plugin includes:

• MCP server auto-installed via uvx
• Agent skill teaching Claude about the server's 30-90+ tools, safety model, and efficient usage patterns
• Interactive /setup command that walks you through connecting to your controller and writes credentials to .claude/settings.local.json (gitignored, never committed)
• Cross-platform support (bash + PowerShell)

Plugin versions auto-sync with PyPI releases via CI, so marketplace users always get the latest.

Auto-Generated Tool References

Each plugin's skill includes a complete tool reference (every tool name, type, description) that's auto-generated from the tool manifests. A CI workflow catches drift — if tools change in the server but the skill reference isn't updated, the PR fails. No stale docs.

What's Next

• Drive server (planned)
• Cross-server scenarios plugin (when there's demand)
• Continued expansion of Network, Protect, and Access tool coverage

All three servers are available now. Try them out and let us know how it goes.