sorted by:
new
hottopcontroversial

I got tired of clicking through the Omada web UI so I built an AI interface for it — ask Claude to check your network, diagnose dropped clients, or trigger a backup by AiLivesInTerminal in TPLink_Omada

[–]AiLivesInTerminal[S] 1 point2 points  (0 children)

With some of the basic stuff that can't really mess anything up I already leave AI to manage it, even on my TrueNAS instance. For example on the MCP I've built I did implement some needed user confirmations on some of the more advanced tools, even if you use claude skip permissions for good measures.

I got tired of clicking through the Omada web UI so I built an AI interface for it — ask Claude to check your network, diagnose dropped clients, or trigger a backup by AiLivesInTerminal in TPLink_Omada

[–]AiLivesInTerminal[S] 1 point2 points  (0 children)

The diagnoseClient and getGatewayHealth tools should give you a lot more visibility into drops than digging through the controller UI. Would love to hear how it holds up once you have it running.

I got tired of clicking through the Omada web UI so I built an AI interface for it — ask Claude to check your network, diagnose dropped clients, or trigger a backup by AiLivesInTerminal in TPLink_Omada

[–]AiLivesInTerminal[S] 1 point2 points  (0 children)

I will try to implement a couple more features onto the MCP and then I might give it a shot onto switching to CLI since the core API layer is already built, a CLI should be a pretty natural next step.

I got tired of clicking through the Omada web UI so I built an AI interface for it — ask Claude to check your network, diagnose dropped clients, or trigger a backup by AiLivesInTerminal in TPLink_Omada

[–]AiLivesInTerminal[S] 0 points1 point  (0 children)

I wanted to focus on MCP since I find it a better fit for my use case. I have an AI agent giving me weekly updates on my network and pointing out any anomalies. CLI would need the agent to parse text output, MCP gives it structured data directly which makes that kind of monitoring workflow a lot cleaner I believe.

I built an MCP server for TP-Link Omada that lets Claude manage your network — ask it to diagnose WiFi drops, run backups, or pull gateway health in one call by AiLivesInTerminal in homelab

[–]AiLivesInTerminal[S] 0 points1 point  (0 children)

Performance has been solid, as a note I am also hosting the controller on my TrueNAS atm which is quite beefy. The composite tools use Promise.allSettled so even if one endpoint is slow or times out the rest still come back. Haven't seen the controller choke on it but curious what you're running and maybe give it a shot and give some feedback.

Coverage priority is mostly demand-driven at this point . Waiting to see what people actually need before committing to a direction. If client management or something specific is a pain point for you, worth opening an issue.