Developer Tools & Devops · UniFi + Claude
UniFi MCP with Claude: Monitor Network Health and Inventory in Plain Language
The short answer
Claude connects to UniFi through the Model Context Protocol (MCP), a secure standard that lets Claude read data from UniFi and carry out permitted actions. Using an API key, Claude can check site inventory, internet health and SD-WAN configurations, then summarise network status in plain English for your team.
What is UniFi?
UniFi is Ubiquiti's network management platform. It gives IT and operations teams a single place to manage sites, network devices and connectivity. Teams use it to track inventory across locations, watch internet health, and review SD-WAN status. It suits multi-site businesses, managed service providers, offices, hotels, schools and any organisation that depends on reliable connectivity across several locations.
How Claude connects to UniFi through MCP
The Model Context Protocol (MCP) is an open standard that lets Claude securely use other software. Think of it as a universal adapter between Claude and a tool. For UniFi, an MCP server or a direct API connection carries requests from Claude to your UniFi account and back again, using the permissions you set.
Once connected, Claude can read site inventory, check the health of internet connections, review SD-WAN configurations and pull together a summary of network status. Someone on your team can simply ask, for example, which sites have degraded internet links this morning, and receive a clear answer with the supporting details.
Access is controlled by the API key you issue, and we set it up with least-privilege access so Claude sees only what it needs. Read-only monitoring is the usual starting point. Any change to network configuration can be routed to a named person for approval, so your people stay in charge of consequential decisions.
What you can automate
Morning network health briefing
Each morning Claude reviews internet health across your sites and produces a short briefing. It highlights links with unusual latency, packet loss or outages, so the IT lead starts the day knowing where to look first rather than checking dashboards one by one.
Site inventory questions
Operations managers can ask in plain language how many access points or switches are deployed at each location, or which devices are nearing end of life. Claude pulls the answer from UniFi, saving time spent exporting spreadsheets and cross-checking records.
SD-WAN configuration reviews
When a new branch is being planned, Claude can review existing SD-WAN configurations and summarise how similar sites are set up. This helps network engineers keep designs consistent and spot gaps before a rollout.
Incident summaries for leadership
After a connectivity problem, Claude can compile the affected sites, duration and likely scope into a clear note for management. Non-technical leaders get the facts without waiting for a technical write-up.
Monthly connectivity reporting
Claude can gather internet health and device inventory data across the month and draft a report with trends, such as sites that repeatedly underperform. Finance and operations teams can use this to review providers and budgets.
An end-to-end workflow: Branch outage to ticket and notification
TriggerClaude detects an internet health drop at a branch office in UniFi during its scheduled check.
Claude reads the affected site's connection status and recent health history from UniFi.
Claude summarises the likely scope, such as whether SD-WAN failover has engaged.
Claude opens a ticket in your IT service desk system with the summary and affected site details.
Claude posts a short alert to the branch manager and IT lead in Microsoft Teams.
A network engineer reviews the ticket and approves any configuration change before it is made.
Once health returns to normal, Claude adds a resolution note to the ticket.
OutcomeTypically faster triage of connectivity issues, with branch staff informed earlier and a complete record kept for later review.
How we set it up
Free automation audit
We review how your network team currently monitors sites, devices and connectivity, and identify the workflows worth automating first. There is no charge for this session.
Secure connection
We connect Claude to UniFi using an API key, either through an MCP server or a direct API connection, depending on what suits your setup. Access is limited to the permissions the key needs.
Workflow design
We design the end-to-end workflow across UniFi and your other systems, such as Microsoft 365 or your ticketing tool, with clear approval points for consequential actions.
Testing and launch
We test the workflow against real past incidents and inventory questions, then launch with monitoring and audit logs so every action can be traced.
Team training
We train your network, IT and operations staff to ask questions, review Claude's summaries and manage approvals, so the team owns the system from day one.
Who benefits
- IT and network managers
- Faster visibility into site health and fewer manual checks across locations.
- Operations directors
- Plain-language answers about inventory and connectivity without waiting for reports.
- Managed service providers
- Consistent monitoring across client sites with summaries ready for account reviews.
- Leadership teams
- Clear, non-technical updates after incidents and during planning.
Security and control
- Least-privilege API key access, so Claude sees only the data it needs.
- Read-only monitoring by default, with changes routed to a named approver.
- Audit logs that record every request Claude makes to UniFi.
- Regular review of the API key and its permissions, with prompt revocation if needed.
- Human sign-off on any network configuration change before it takes effect.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can host their Claude workflows in those regions to align with local expectations on data handling. In India, we design workflows to meet the Digital Personal Data Protection Act, 2023, where personal data is involved. For organisations in the UAE and Saudi Arabia, we consider local data protection laws when choosing a hosting region. Hosting region is selected to meet each client's specific requirements.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the UniFi MCP server do?
The UniFi MCP server acts as a secure bridge between Claude and your UniFi account. It lets Claude read information such as site inventory, internet health and SD-WAN status, and carry out permitted actions. You control which actions are allowed, and the server only exposes what you have authorised.
Is connecting Claude to UniFi secure?
Security depends on how the connection is set up. We use an API key with least-privilege access, limit Claude to the data it needs, keep audit logs of every request, and require human approval for configuration changes. We also recommend regular reviews of the key and prompt revocation if it is ever exposed.
What can Claude do with UniFi once connected?
Claude can check site inventory, review internet health, examine SD-WAN configurations and summarise overall network status in plain language. It can answer questions from your team, produce reports and feed information into other systems, subject to the permissions you grant.
How long does setup take?
Timelines vary with the number of sites, the complexity of the workflows and how many other systems are involved. A focused read-only monitoring setup is often quicker than a full workflow that includes approvals and ticketing. We confirm the timeline during the free automation audit.
Which plan or permissions do I need?
You need a UniFi account with an API key that has the permissions required for the data you want Claude to read. The exact access depends on your UniFi setup and how your organisation manages its accounts. We check these requirements during the audit and recommend the narrowest permissions that support your workflow.