01
AI operating costs
Model usage for development, code review, compatibility research, test generation, release notes, and documentation.
Sustain the project
Keep UniFi MCP reliable for real deployments.
UniFi MCP is an independent open-source project that gives AI agents safe, structured access to UniFi Network, Protect, and Access controllers. Sponsorship funds the work that keeps it useful as UniFi firmware, MCP clients, Python packages, agent tooling, and controller APIs keep moving.
Maintenance budget
The work behind a reliable agent-to-controller bridge.
Sponsorship is not a feature bounty system. It funds the unglamorous maintenance work that keeps a local-first UniFi automation stack dependable.
02
Controller reality checks
Real-device probes catch UniFi field names, endpoint behavior, permission gaps, and firmware changes before users find them.
03
Release work
Versioning, changelogs, manifests, plugin packaging, Docker images, PyPI publishing, npm relay updates, and regression checks.
04
Community support
Issue triage, setup guidance, docs, examples, and patterns that keep controller-changing tools safe by default.
Simple options
Pick the level that matches how much UniFi MCP saves you.
A small set of tiers keeps the ask clear. These links carry project and tier metadata for sponsorship exports; GitHub will still ask you to choose or confirm the matching tier.
$5 / month
Supporter
For users who want the project to keep shipping fixes, docs, and compatibility updates.
$15 / month
Power user
Helps cover recurring AI maintenance costs and live compatibility checks across the active server packages.
$50 / month
MSP / team backer
For teams, homelab power users, and MSPs relying on UniFi MCP in repeatable workflows.
$25+ one time
Thank-you contribution
A direct way to support a release, bug fix, compatibility update, or doc improvement that helped your setup.
Want to make a larger one-time contribution, sponsor as a company, or fund a specific compatibility push? Use a custom amount on GitHub Sponsors or start a roadmap discussion first.
Boundaries
What sponsorship does and does not change.
The project stays open, local-first, safety-minded, and independent.
No paywall
Core packages, plugins, docs, and safety patterns remain open source under the MIT license.
No unsafe shortcuts
Sponsorship does not bypass preview-then-confirm mutations, permission gates, or compatibility checks.
No guaranteed feature queue
Sponsors help sustain the project, but roadmap decisions still follow user impact, safety, and maintainability.
Help keep UniFi MCP maintained.
Recurring sponsorship is the strongest signal that this project should keep getting real maintenance time, AI-assisted development budget, and controller compatibility testing.