Skip to main content
Glama
aljopro
by aljopro

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OMADA_SITE_IDNoSite ID (optional but recommended; site-scoped tools need it somewhere)
OMADA_BASE_URLYesBase URL of the TP-Link Omada controller, e.g. https://your-controller:8043
OMADA_CLIENT_IDYesClient ID from Settings -> Platform Integration -> Open API
OMADA_OMADAC_IDYesOmada controller ID, obtainable from GET /api/info (result.omadacId)
OMADA_STRICT_SSLYesSet to 'false' to disable SSL certificate verification, as controllers use self-signed certificatesfalse
MCP_HTTP_BIND_ADDRNoAddress to bind the HTTP server to, e.g. 0.0.0.0
MCP_SERVER_USE_HTTPNoSet to 'true' to run the server in HTTP mode instead of stdio
OMADA_CLIENT_SECRETYesClient secret for the Open API application
OMADA_TOOL_CATEGORIESNoCategory filter controlling which tools are exposed. Default is 'dashboard:r,client-insights:r,clients:r,devices-all:r'; use 'all:r,generic:rw,clients:rw' to enable everything.dashboard:r,client-insights:r,clients:r,devices-all:r

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription

No tools

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

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/aljopro/tplink-omada-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server