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.1456 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables call-recording upload and retrieval, compliance metadata and tag management, group/account/user administration, REST-hook (webhook) notifications, and Dub.Point telecom-system integration against the Dubber platform. All destructive operations are consent-gated and confirmation-protected.Apache 2.0
- FlicenseNot 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.-

Skysay MCPofficial
AlicenseNot gradedqualityBmaintenanceConnects AI assistants to an existing Skysay workspace so they can inspect and manage voice agents, phone numbers, calls, SMS messages, and campaigns, with a read-only endpoint available for fixed read-only access.MIT- 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.1057 PyPI40MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents and applications to interact with UniFi network infrastructure through the UniFi Network Controller API, supporting device, client, network, firewall, QoS, backup, multi-site, and topology management.40 npmApache 2.0
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.