tplink-omada-mcp
by MiguelTVMS
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HTTP_PATH | No | Base path for MCP endpoints | /mcp |
| MCP_HTTP_PORT | No | Port for the HTTP server | 3000 |
| OMADA_SITE_ID | No | Optional default site ID; if omitted, each MCP call must pass a siteId | |
| OMADA_TIMEOUT | No | HTTP request timeout in milliseconds | 30000 |
| OMADA_BASE_URL | Yes | Base URL of the Omada controller (e.g., https://omada-controller.local) | |
| OMADA_CLIENT_ID | Yes | OAuth client ID generated under Omada Platform Integration | |
| OMADA_OMADAC_ID | Yes | Omada controller ID (omadacId) to target | |
| OMADA_STRICT_SSL | No | Enforce strict SSL certificate validation (set to 'false' for self-signed) | true |
| MCP_HTTP_BIND_ADDR | No | Bind address (IPv4/IPv6). Use adapter IP address to expose to the network. | 127.0.0.1 |
| MCP_HTTP_ALLOW_CORS | No | Enable CORS for the HTTP server | true |
| MCP_SERVER_USE_HTTP | No | Start HTTP server instead of stdio | false |
| OMADA_CLIENT_SECRET | Yes | OAuth client secret associated with the client ID | |
| MCP_SERVER_LOG_LEVEL | No | Logging verbosity (debug, info, warn, error, silent) | info |
| MCP_SERVER_LOG_FORMAT | No | Log output format (plain, json, or gcp-json) | plain |
| OMADA_TOOL_CATEGORIES | No | Comma-separated categories to enable at startup | dashboard:r,client-insights:r,clients:r,devices-all:r |
| MCP_HTTP_NGROK_ENABLED | No | Use ngrok to expose the HTTP server publicly | false |
| MCP_HTTP_ALLOWED_ORIGINS | No | Comma-separated list of allowed origins. Use '*' to allow all (dev only) | 127.0.0.1, localhost |
| MCP_HTTP_HEALTHCHECK_PATH | No | Path for the healthcheck endpoint | /healthz |
| MCP_HTTP_NGROK_AUTH_TOKEN | No | Ngrok auth token (required if MCP_HTTP_NGROK_ENABLED=true) | |
| MCP_HTTP_ENABLE_HEALTHCHECK | No | Enable a healthcheck endpoint | true |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/MiguelTVMS/tplink-omada-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server