iKuai MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IKUAI_URL | Yes | The URL of the iKuai router (e.g., http://192.168.9.1) | |
| IKUAI_PASSWORD | Yes | Password for the iKuai router | |
| IKUAI_USERNAME | Yes | Username for the iKuai router |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 229 tools
With 229 tools, many have overlapping purposes such as multiple get/list monitoring tools (get_line_monitoring, get_terminal_list, get_load_monitoring) and numerous log retrieval functions. Duplicate tools like get_ddns_config and get_dynamic_dns_config further confuse selection, making it nearly impossible for an agent to reliably distinguish between them.
The majority of tools follow a verb_noun pattern (list_*, get_*, add_*, delete_*, set_*, toggle_*), but the choice between get_ and list_ is inconsistent (list_wan_configs vs get_wan_status). Outliers like kick_pppoe_user, wake_on_lan, subnet_calculator, and change_admin_password deviate from the pattern, though overall naming remains readable.
229 tools is drastically excessive for an MCP server. Even for a comprehensive router management system, this volume overwhelms agents and violates the principle of a well-scoped toolset, far exceeding the 3-15 tool sweet spot.
The toolset thoroughly covers router domains: interfaces, VPN, DHCP, DNS, routing, NAT, firewall, QoS, logs, and system utilities. However, many resources lack update/modify operations (e.g., VLAN, DHCP static bindings, IP groups), and the presence of duplicates suggests minor workflow gaps.