Device Management
UniFi MCP connector
Connect UniFi to Elaichi and Claude, ChatGPT, Cursor, or any MCP client can list your UniFi devices, hosts, sites, SD-WAN configurations and ISP metrics, and manage console paths, with every request running as the signed-in person and recorded in an audit log.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect UniFi to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect UniFi once
-
Open Connections, choose Add connection, and pick UniFi.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste an UniFi API key. One person generates a token in UniFi and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect UniFi to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect UniFi to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect UniFi to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect UniFi to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with UniFi through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
IT
Check which devices are online before a ticket escalates
Ask which UniFi devices and hosts are registered across your sites and get a plain list back, so the help desk can confirm what is out there before anyone walks to a closet.
-
Network operations
Review SD-WAN status across every site
Pull the current SD-WAN configurations and their status in one question, then spot the site whose configuration has not come up cleanly.
-
Managed services
Give a client a site inventory in minutes
List the UniFi sites, hosts and devices you manage for a customer and turn them into a summary for the monthly review, without opening each console by hand.
-
IT
Explain a slow connection with ISP metrics
When someone says the internet is slow, ask for the ISP metrics for that site and answer with real latency and throughput numbers instead of a guess.
-
Network operations
Keep console paths tidy as sites change
Create a console path for a new location, update the ones that moved, and clear out the stale ones in bulk, all from a single conversation.
-
Office management
Confirm what is installed at a new office
Before the move-in day, ask which UniFi hosts and devices are already registered at the new site so you know what still needs to be plugged in.
Try asking
- “List every UniFi site with offline devices right now”
- “Show ISP metrics for our three busiest UniFi hosts”
- “Which UniFi SD-WAN configs changed status this week”
AI tools
UniFi tools for your AI agents
14 tools are ready to call through Elaichi's MCP endpoint the moment you connect UniFi, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting UniFi gets you
6 screens from the product, each doing one job for your UniFi account.
The agent
Ask about sites and devices, get answers.
Plain language questions answered from live UniFi hosts, sites and devices.
- devices
- hosts
- sites
- console paths
Ask Elaichi to work across your apps.
List every UniFi site with offline devices right now
Show ISP metrics for our three busiest UniFi hosts
Which UniFi SD-WAN configs changed status this week
Also runs in Claude, ChatGPT or Cursor
MCP clients
One UniFi endpoint for every MCP client.
Claude, ChatGPT and Cursor connect over OAuth, no SDK, no shared API key.
Copy the endpoint
Tool catalog
14 UniFi tools ready, no custom code.
Devices, hosts, sites, SD-WAN configs, ISP metrics and console paths, already wired.
- List all UniFi devices
- List all UniFi hosts
- Get single UniFi host by ID
- List all UniFi sites
Toolboxes
Every team gets its own UniFi toolbox.
Curate one toolbox for network ops, another for support, each scoped separately.
- Network operations
- Support
- Field deployment
- IT security
Shared connections
Share UniFi access, never share credentials.
Teammates query sites and devices through a connection they can never read.
- Head office
- Retail sites
- EMEA network
- Support tier one
Audit log
Every UniFi call is on the record.
When, who, what happened, type and resource, appended and never edited.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires, UniFi work gets done.
Fetch devices, group them, draft a digest, approve it, post back to UniFi.
UniFi digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch devices
UniFi
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
UniFi
Queued
Collections and dashboards
UniFi health, counted rather than requested.
Four metrics, 14 days of records created, split by team, refreshed on schedule.
UniFi health
Refreshed 4 minutes ago · every 15 minutes · from the devices collection
Devices
1,284 ↓ 12%
Hosts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Devices created
Last 14 days
By team
Share of activity
Head office 34%
Retail sites 27%
EMEA network 21%
Support tier one 18%
FAQ
Frequently asked questions
How do I connect UniFi to Claude?
Connect UniFi in Elaichi first by pasting the API key from your UniFi account; there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi as yourself, and from then on your UniFi devices, hosts and sites are available in the conversation.
Does UniFi work with ChatGPT and Cursor as well as Claude?
Yes. Once UniFi is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect UniFi once and every client you use picks it up.
What can an AI agent actually do with my UniFi data?
An agent connected to UniFi through Elaichi can list your devices, hosts and sites, look up a single host, read your SD-WAN configurations and their current status, and pull ISP metrics for a site. It can also create, update and remove console paths, including in bulk. It cannot reboot devices or change network settings, because this connector does not include those actions.
Does connecting UniFi give the AI access to my whole network?
No. Everything the agent does in UniFi runs under the API key of the person who connected it, so it sees only the sites and consoles that key can already reach. Elaichi can narrow that further, for example to read-only questions about devices and ISP metrics, but it can never widen access beyond what UniFi itself allows.
Can I stop an agent from deleting or changing things in UniFi?
Yes. Restrictions in Elaichi apply per action, so you can allow listing UniFi devices, hosts and SD-WAN status while blocking the creation, update or bulk deletion of console paths. A blocked action is never shown to Claude, ChatGPT or Cursor at all, so no prompt, however worded, can reach it.
What happens to a UniFi connection when someone leaves?
When you offboard someone in Elaichi, their access to UniFi through every client ends at once. If they had shared a UniFi connection with the team, it keeps working for everyone else. If you want it gone entirely, disconnecting UniFi once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.
Put UniFi in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.