unifi-talk-mcp
Related Servers
Alternatives to unifi-talk-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceProvides read-only access to UniFi Network consoles for sites, devices, clients, vouchers, networks, Wi-Fi, and firewall configuration, with optional opt-in tools for controlled write operations and legacy controller support.1463 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables read-only querying of a UniFi fleet via the Site Manager API and per-console connector proxy, allowing users to list hosts, sites, devices, ISP metrics, and live network clients through Claude.Academic Free v1.1
- AlicenseAqualityAmaintenanceQueryable UniFi API documentation for Network, Protect, Site Manager, InnerSpace, Mobility and Carrier Fabric - endpoint search, schema drill-down and code examples in five languages. Read-only: it serves scraped docs and never connects to a controller.1210119 PyPI37MIT
- FlicenseAqualityDmaintenanceProvides complete programmatic access to the Retell AI platform, enabling autonomous management of voice and text agents, telephony, and monitoring.60-
- AlicenseNot gradedqualityCmaintenanceEnables building, publishing, and operating CallDeskTech voice agents, including conversation flows, knowledge bases, phone routing, calls, batch calls, and webhooks.MIT
- FlicenseAqualityBmaintenanceProvides read-only access to Yeastar P-Series PBX System APIs, enabling querying of extensions, groups, trunks, routes, IVR menus, ring groups, queues, live call and agent status, contacts, call detail records, reports, and system metadata for AI assistants.26-
TDQS
Scored across 7 tools
Most tools have clearly distinct purposes: status, write operations, call history, call detail, devices, endpoint catalog, and generic reads. Slight overlap exists between talk_get_call (specialized call timeline) and talk_get (generic read by endpoint id), but descriptions clarify the intended use.
All tools share the talk_ prefix and mostly follow verb_noun (talk_list_calls, talk_get_call, talk_list_devices). talk_status and talk_invoke deviate slightly from the pattern, but the naming remains predictable and readable.
Seven tools is well-scoped for a UniFi Talk integration: a status check, a write dispatcher, a catalog of endpoints, and a few high-value read wrappers. Each tool earns its place without redundancy or bloat.
The combination of generic talk_get for reads, talk_invoke for writes, and talk_list_endpoints for discoverability covers the full API surface. Convenience tools for calls and devices cover the most common workflows, so there are no obvious dead ends.