A
licenseA
qualityD
maintenanceA Model Context Protocol server that enables AI assistants to read and safely modify TP-Link Omada networks through capability-gated tools, with a default read-only profile and dry-run writes for security.
11
MIT
TP-Link Omada MCP server
Related Servers
Alternatives to TP-Link Omada MCP server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceExposes TP-Link Omada controller APIs to AI copilots, enabling listing of sites, devices, and clients, and executing arbitrary Omada API calls via natural language.8420MIT
- AlicenseBqualityFmaintenanceSecurity-focused MCP server for TP-Link Omada Open API workflows, enabling network management via natural language.8721MIT
- AlicenseAqualityAmaintenanceRead-only MCP server for TP-Link Omada SDN controllers, enabling querying controller, site, device, and WiFi state.8Apache 2.0
- AlicenseCqualityCmaintenanceA Model Context Protocol (MCP) server for UniFi Network Controllers that enables LLMs to interact with UniFi infrastructure for monitoring and control.51MIT
- AlicenseAqualityBmaintenanceA Model Context Protocol server that enables AI assistants like Claude to interact directly with Home Assistant, allowing them to query device states, control smart home entities, and perform automation tasks.16340MIT
TDQS
B3.2/5.0
Scored across 84 tools
Disambiguation5/5
Each tool targets a specific resource and aspect (e.g., AP radios, VLAN config, cable test logs), with clear descriptions that differentiate even similar tools. Deprecated tools are explicitly marked, reducing ambiguity.
Naming Consistency5/5
Tool names follow a consistent verb_noun snake_case pattern (e.g., getApDetail, listDevices, getDashboardOverview). Verbs like 'get', 'list', 'search', 'trigger' are used predictably, with minor exceptions that do not hinder coherence.
Tool Count2/5
With 84 tools, the server is overpopulated for an MCP context. While the domain (network management) can be complex, the number far exceeds typical well-scoped sets (3-15), making it unwieldy for an agent to navigate effectively.
Completeness2/5
The tool set is heavily read-only, lacking any create, update, or delete operations for configurations. This is a significant gap for a management server, as agents cannot perform essential lifecycle tasks beyond retrieving data and triggering a few actions.
Maintenance
ActivityMaintained
ResponsivenessSyncing