omada-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OMADA_PEM | No | Path to the pinned controller.pem | |
| OMADA_CONFIG | No | Path to controller.json | |
| OMADA_BASE_URL | No | Controller base URL | |
| OMADA_CLIENT_ID | No | Open API Client-mode application Client ID | |
| OMADA_OMADAC_ID | No | Controller ID from /api/info | |
| OMADA_CERT_SHA256 | No | SHA-256 of the controller's leaf certificate | |
| OMADA_CREDENTIALS | No | Path to a credentials JSON file | |
| OMADA_ACCESS_TOKEN | No | Pre-fetched OAuth access token | |
| OMADA_CLIENT_SECRET | No | Open API Client-mode application Client Secret | |
| OMADA_ENABLE_WRITES | No | Set to true to register the write tools; omitted/false = read-only (default) | false |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getConnectionStatusA | Report configured connection state without logging in or making a network call. |
| listSitesA | List sites available to the configured credential. |
| listDevicesB | List adopted devices for the selected site. |
| listClientsB | List active clients for the selected site. |
| getLanNetworksA | Read VLAN/subnet/DHCP settings for the selected site. Contains no SSID passwords. |
| readSiteConfigurationC | Read one fixed configuration dataset. No arbitrary paths or methods; unknown datasets are rejected. |
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 6 tools
Most tools have clear, distinct targets: connection status, sites, devices, clients, LAN networks, and site configuration. The only mild ambiguity is between getLanNetworks and readSiteConfiguration, since both read configuration-like data, but the former is explicitly VLAN/subnet/DHCP-specific.
All tool names use camelCase and begin with readable verbs such as get, list, and read. The verb choice varies slightly, but the pattern remains predictable and understandable.
Six tools is a reasonable minimum for a read-only Omada surface, but the set feels thin for practical exploration and management. It covers basic listing and status reads without becoming bloated.
The surface is intentionally read-only and covers core list/status/configuration reads, but it lacks detail-oriented operations such as getting a specific device or client, reading SSID/wireless configuration, or any write/update lifecycle operations. Agents can perform basic inspection but may hit dead ends for deeper troubleshooting.