mcp-omada
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OMADA_PASS | No | Legacy local-user login password | |
| OMADA_USER | No | Legacy local-user login username | |
| OMADA_SITE_ID | No | Site to operate on; auto-selected if the controller manages exactly one site (legacy auth only) | |
| OMADA_TIMEOUT | No | HTTP request timeout, in seconds | 15 |
| OMADA_BASE_URL | Yes | Controller base URL, e.g. https://192.168.1.2:8043 | |
| OMADA_CLIENT_ID | No | Open API client ID | |
| OMADA_LOG_LEVEL | No | Log level for the server process (stderr) | INFO |
| OMADA_OMADAC_ID | No | Controller ID; auto-discovered via GET /api/info if unset | |
| OMADA_VERIFY_TLS | No | Verify the controller's TLS certificate | false |
| OMADA_CLIENT_SECRET | No | Open API client secret |
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
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/thalisantunes/mcp-omada'
If you have feedback or need assistance with the MCP directory API, please join our Discord server