UnifiyMe
# UnifiyMe
A Model Context Protocol (MCP) server for UniFi Network Controllers. This server allows you to interact with your UniFi network infrastructure through LLMs, providing both high-level monitoring and deep system-level control.
## Features
- **Network Monitoring**: Quick overview of devices, clients, and site health.
- **Client Management**: Block/unblock clients, force reconnections, and search historical connection data.
- **Physical Control**: Power cycle PoE ports and flash device LEDs for easy location.
- **Advanced Analytics**: Deep Packet Inspection (DPI) stats, subsystem health, and alarm tracking.
- **Guest Access**: Create guest WiFi vouchers on the fly.
- **SSH Diagnostics**: Execute commands directly on the router and fetch system logs for deep troubleshooting.
- **Discord Integration**: Manage and monitor your network directly from Discord.
- **Prometheus Exporter**: Export UniFi metrics to Prometheus for long-term monitoring and alerting.
- **Grafana Dashboards**: Pre-configured dashboards for visualizing network health and performance.
- **Restricted YouTube Blocker**: Specialized tools for managing YouTube access via UniFi firewall rules.
## Optimization
This server includes specialized optimizations for UniFi controllers:
- **Monkey-patched Session Management**: Reduces redundant heartbeat checks, cutting request overhead by up to 50%.
- **Intelligent Caching**: 10-second TTL cache for frequent lookups to improve responsiveness and reduce controller load.
## Reliability & Security
- **Persistence Layer**: Automated background monitoring ensures that critical traffic rules (like YouTube blocking) are re-enforced every 60 seconds if they are tampered with.
- **Health Monitoring**: Integrated `/health` endpoint and Docker health checks ensure maximum uptime and automated container recovery.
- **API Hardening**: All Gateway actions are strictly validated with MAC address regex and required field checks.
- **Secure Reverse Proxy**: Pre-configured Caddy integration for automated TLS/HTTPS termination.
## Setup
1. Clone the repository.
2. Install dependencies:
```bash
npm install
```
3. Create a `.env` file with your UniFi credentials:
```env
UNIFI_HOST=https://your-unifi-controller-ip
UNIFI_USERNAME=your-username
UNIFI_PASSWORD=your-password
UNIFI_SITE=default
# Optional: SSH Credentials for diagnostics
SSH_HOST=192.168.1.1
SSH_USERNAME=root
SSH_PASSWORD=your-ssh-password
# Optional: Discord Bot Configuration
DISCORD_TOKEN=your-discord-bot-token
DISCORD_CLIENT_ID=your-discord-client-id
```
4. Build the project:
```bash
npm run build
```
## Usage
### 1. Installation via npm (Published)
This is the recommended way for most users. You can run the server directly using `npx` in your Claude Desktop configuration.
Add this to your `claude_desktop_config.json`:
```json
{
"mcpServers": {
"unifyme": {
"command": "npx",
"args": ["-y", "unifiyme"],
"env": {
"UNIFI_HOST": "https://<CONTROLLER-IP>",
"UNIFI_USERNAME": "<YOUR-USERNAME>",
"UNIFI_PASSWORD": "<YOUR-PASSWORD>",
"UNIFI_SITE": "default"
}
}
}
}
```
### 2. Local Development Setup
If you prefer to run from source or are contributing:
1. Clone the repository.
2. Install dependencies: `npm install`
3. Build the project: `npm run build`
4. Use the following config:
```json
{
"mcpServers": {
"unifyme": {
"command": "node",
"args": ["/path/to/UnifiyMe/dist/index.js"],
"env": {
"UNIFI_HOST": "...",
"UNIFI_USERNAME": "...",
"UNIFI_PASSWORD": "...",
"UNIFI_SITE": "default"
}
}
}
}
```
### Discord Bot
To start the Discord bot:
```bash
npm run start # If built
# OR
npm run dev # For development
```
### Prometheus Exporter
The server automatically starts a Prometheus exporter on port 9090 (configurable). Metrics are available at `/metrics`.
### Docker Support
You can run the entire stack (UnifiyMe, Prometheus, Grafana) using Docker Compose:
```bash
docker-compose up -d
```
## Tools
### Monitoring & Discovery
- `get_network_status`: Get overall network health and status.
- `list_devices`: List all network devices (APs, switches, gateways).
- `list_clients`: List all connected network clients.
- `get_device_details`: Get detailed information about a specific device.
- `search_network`: Search for devices or clients by IP, MAC, hostname, or alias.
- `get_bandwidth_stats`: Get top bandwidth consumers.
- `get_network_topology`: Get network topology (simplified view of uplinks).
- `get_client_history`: Search historical client data.
- `get_network_health`: Get detailed subsystem health status.
- `get_alarms`: List recent alerts and IPS/IDS events.
- `get_dpi_stats`: Get application usage statistics.
- `get_wlan_config`: Get WiFi network configurations (SSIDs, security, etc.).
- `get_network_config`: Get logical network configurations (VLANs, subnets, DHCP).
- `get_firmware_status`: Check for available firmware updates across all devices.
- `get_firewall_rules`: Get all configured firewall rules.
- `get_firewall_groups`: Get all configured firewall groups (IP, Port).
- `get_deep_dive`: Perform a deep dive into network health, DPI stats, and active client traffic.
- `get_events`: Get recent network events.
### Control & Management
- `reboot_device`: Restart a device by MAC address.
- `cycle_poe_port`: Power cycle a PoE port on a switch.
- `locate_device`: Flash/Stop flashing the LED on a device.
- `block_client` / `unblock_client`: Manage network access for clients.
- `reconnect_client`: Force a client to reconnect.
- `create_voucher`: Create guest WiFi vouchers.
- `set_client_user_group`: Assign a client to a specific user group (for throttling).
- `create_user_group`: Create a new user group with bandwidth limits.
### Specialized Management
- `block_restricted_youtube` / `unblock_restricted_youtube`: Manage YouTube access for Restricted devices.
- `get_restricted_youtube_status`: Check current YouTube blocking status for Restricted.
- `detect_iot_devices`: Identify potential IoT devices not on the IoT VLAN.
- `migrate_iot_devices`: Propose migration of detected IoT devices to a target network.
- `enforce_iot_limits`: Throttle high-bandwidth IoT devices.
- `protect_vips`: Ensure VIP devices are not throttled.
- `ensure_traffic_rule`: Create or update complex traffic rules.
### Diagnostics (SSH)
- `run_ssh_command`: Execute a command directly on the router.
- `get_router_logs`: Fetch system logs from the router.
## Contributing
Contributions are welcome! Please see [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines on how to report issues, suggest features, and submit pull requests.
## License
This project is licensed under the [MIT License](LICENSE).
TDQS
Scored across 51 tools
Multiple tools have unclear boundaries, especially between get_network_status, get_network_health, and get_deep_dive, as well as between get_bandwidth_stats, get_dpi_stats, and get_client_dpi. The ensure_ vs update_ rule pairs also overlap in purpose, making it easy for an agent to pick the wrong tool.
Most tools follow a readable verb_noun pattern, but read operations inconsistently mix get_, list_, and search_. The ensure_ and update_ rule tools are also semantically redundant in naming, though the overall style is still understandable.
With 51 tools, this server is extremely large and unwieldy for an agent to navigate. Many health, DPI, client, and rule-management operations could be consolidated, and the sheer count creates significant selection overhead.
Read coverage is broad: status, topology, devices, clients, configs, firewall rules, port forwards, traffic rules, groups, and tags are all present. However, several lifecycle gaps exist, including no create/update/delete for Wi-Fi or network configs, no update/delete for firewall rules or user groups, no firmware upgrade action, and no voucher management beyond creation.