omada-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | debug / info / warn / error. | info |
| MCP_HTTP_BIND | No | Loopback bind when HTTP lands. | 127.0.0.1 |
| MCP_HTTP_PORT | No | 3000 | |
| MCP_TRANSPORT | No | stdio only; setting http throws today. | stdio |
| OMADA_SITE_ID | No | Default site; otherwise tools need siteId. | |
| OMADA_BASE_URL | Yes | Controller URL, no trailing slash. | |
| MCP_HTTP_ENABLE | No | Reserved for the future HTTP transport. | false |
| OMADA_CLIENT_ID | Yes | From the Open API app. | |
| OMADA_OMADAC_ID | Yes | Controller ID. | |
| OMADA_TIMEOUT_MS | No | HTTP timeout. | 30000 |
| OMADA_VERIFY_TLS | No | false for self-signed. | true |
| OMADA_DOTENV_PATH | No | Explicit override path to a .env file. Useful when the MCP client launches the server without a predictable cwd. | |
| OMADA_CLIENT_SECRET | Yes | From the Open API app. Never logged. | |
| OMADA_CAPABILITY_PROFILE | No | safe-read / ops-write / admin. | safe-read |
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 |
|---|---|
| list_sitesA | List all sites on the Omada controller. Returns each site's id, name, region and time zone — useful as a starting point and to find the siteId that other tools need. |
| list_devicesA | List APs, switches and gateways at a site, with model, IP, status, firmware version and last-seen timestamp. |
| get_deviceA | Get detail for one device by MAC. For APs, also includes per-band radio config (channel, width, Tx power). Use list_devices to find MACs. |
| get_ap_radiosA | Per-band radio configuration for one AP: channel, channel width, Tx power and Tx-power level for 2.4/5/6 GHz. Use list_devices to find the AP MAC. |
| list_clientsA | List connected clients (wired + wireless) at a site, with SSID, AP, band, channel, RSSI, Tx/Rx rate and total traffic. Also returns site summary counts. |
| get_clientA | Get full detail for one client by MAC: connection (SSID, AP, channel, RSSI, SNR, rates), addressing, traffic, uptime and lifecycle. |
| list_ssidsA | List all SSIDs at a site, grouped by their WLAN group. Returns wlanId/wlanName and the ssidId/ssidName for each SSID — use those ids with get_ssid for full SSID configuration. |
| get_ssidA | Full SSID configuration. If |
| get_site_settingsA | Aggregate site-level wireless settings: roaming (fast roaming, AI roaming, force-disassociation, non-stick, 802.11k report), band steering and mesh. Reads three Open API endpoints in parallel. |
| list_eventsA | Site event log (System / Device / Client events) within a time window. Defaults to the last 24 hours. Returns counts and a sample of entries. |
| list_logsA | Site alert log within a time window. Defaults to the last 24 hours. Optionally filter by module or resolved/unresolved. |
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 11 tools
Most tools target distinct resources or aspects (e.g., clients, devices, events, logs, SSIDs). There is minor overlap between get_device (which includes radio info) and get_ap_radios (which focuses solely on radio configuration), but descriptions differentiate them.
All tool names follow a consistent 'verb_noun' pattern in snake_case (get_*, list_*). No mixed conventions or irregular verbs.
With 11 tools covering sites, devices, clients, events, logs, SSIDs, and settings, the count is well-scoped for a monitoring-oriented MCP server. No excessive or trivial tools.
The tool set covers core read operations for Omada network management (list, get details, settings). Minor gaps exist: no write operations (create/update/delete) and no advanced features like switch port info or topology, but essential monitoring is covered.