Independent maintenance

Support the work.

UniFi MCP is independently maintained. Sponsorship funds the practical work required to keep its controller interfaces, safety model, packages, and documentation useful as the surrounding platforms change.

Maintenance in practice

What support makes possible

Funding goes toward the recurring work behind a dependable open-source project.

Model and agent costs

AI operating costs used for development, review, testing, and documentation.

Live compatibility work

Checks against real UniFi controllers, firmware releases, and hardware classes.

Release maintenance

Publishing and regression work across PyPI, Docker, plugins, the Relay sidecar, and Worker gateway.

Project stewardship

Documentation, issue triage, community support, and security and safety work.

Trust commitments

Project boundaries

Sponsorship sustains the work; it does not change the project’s safety or roadmap standards.

No paywall

Core packages, plugins, documentation, and safety patterns remain open source under the MIT license.

No safety shortcuts

Support never bypasses confirmation, policy gates, review, or compatibility checks.

No purchased feature queue

Roadmap decisions continue to prioritize user impact, safety, and maintainability.