A
licenseB
qualityF
maintenanceSecurity-focused MCP server for TP-Link Omada Open API workflows, enabling network management via natural language.
87
23
MIT
tplink-omada-mcp
by aljopro
Related Servers
Alternatives to tplink-omada-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA 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.111MIT
- AlicenseAqualityAmaintenanceRead-only MCP server for TP-Link Omada SDN controllers, enabling querying controller, site, device, and WiFi state.8Apache 2.0
- AlicenseNot gradedqualityCmaintenanceMCP server for UniFi Network Controller enabling AI assistants to manage UniFi infrastructure via natural language. It supports firewall rules, IPv6, and uses lazy/eager tool modes to minimize context usage.6Mozilla Public 2.0
- AlicenseBqualityCmaintenanceA Model Context Protocol server that exposes TP-Link Omada controller APIs to AI copilots and automation workflows, enabling listing sites, devices, clients, and invoking arbitrary Omada endpoints.84MIT
- AlicenseBqualityCmaintenanceAn MCP server that enables AI assistants to manage UniFi network infrastructure, including cloud management, local network devices, and Protect cameras, through natural language.62MIT
TDQS
C2.8/5.0
Scored across 84 tools
Disambiguation2/5
Many tools overlap heavily, especially around AP and device configuration: getApRadios vs getRadiosConfig, getApDetail vs getApGeneralConfig, and a long list of getSitesAps... getters. Several deprecated tools like getDevice and getClient add further confusion, while listDevices, listDevicesStats, and getAllDeviceBySite have unclear boundaries.
Naming Consistency3/5
Naming is consistently camelCase and mostly follows get/list + resource, but the pattern is not predictable: the same resource appears as getApDetail vs getSitesAps..., getGatewayDetail vs getSitesGateways..., and getGrid.../getDashboard... prefixes are mixed in. The naming is readable but lacks a uniform convention.
Tool Count1/5
84 tools is an extreme count for an MCP server, far beyond the 3-15 well-scoped range. Many tools are micro-getters for single configuration fields that could be consolidated into richer detail endpoints, making the surface unwieldy for agents.
Completeness2/5
The server provides broad read-only coverage of device, client, dashboard, and firmware data, but it is almost entirely observational. There are no create/update/delete operations, no client control, no SSID/WLAN management, and no upgrade/reboot actions; referenced tools like triggerSpeedTest are also missing.
Maintenance
ActivityMaintained
ResponsivenessNo issues