Christoph Emsenhuber
d99d8cf6da
Root cause der Crash-Loops gefunden: - Container bekam Env beim Deploy INLINE (Portainer ignoriert env_file) → alte falsche Var-Namen - jmtvms/tplink-omada-mcp v0.15 nutzt Omada OPEN API (CLIENT_ID/SECRET), nicht user/pass - Transport ist StreamableHTTP (MCP_SERVER_USE_HTTP + MCP_HTTP_*), NICHT SSE/MCP_TRANSPORT Jetzt: /health 200, MCP initialize-Handshake liefert Tools/Capabilities. settings.json → /mcp. .env-Schema, .env.template, compose-Doku korrigiert. Offen: Claude Code reload → VLANs anlegen + .12 adoptieren (Tool-Categories ggf. um write erweitern). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
24 lines
993 B
Plaintext
24 lines
993 B
Plaintext
# omada-mcp Secrets — .env (gitignored). Dieses File = Template, .env = echte Werte.
|
|
#
|
|
# jmtvms/tplink-omada-mcp v0.15: StreamableHTTP-Transport + Omada OPEN API (Client Credentials).
|
|
# Client-Creds erzeugen: Controller-UI → Settings → Platform Integration → Open API →
|
|
# App anlegen (Grant Type: Client Credentials) → liefert Client ID + Client Secret.
|
|
# omadac_id: https://10.40.41.175:8043/api/info → result.omadacId
|
|
# site_id: Controller-UI Site, oder API /{omadacId}/api/v2/sites → result.data[].id
|
|
|
|
# --- Transport: StreamableHTTP auf :3000/mcp ---
|
|
MCP_SERVER_USE_HTTP=true
|
|
MCP_HTTP_BIND_ADDR=0.0.0.0
|
|
MCP_HTTP_PORT=3000
|
|
MCP_HTTP_PATH=/mcp
|
|
MCP_HTTP_ENABLE_HEALTHCHECK=true
|
|
MCP_HTTP_HEALTHCHECK_PATH=/health
|
|
|
|
# --- Omada Open API ---
|
|
OMADA_BASE_URL=https://10.40.41.175:8043
|
|
OMADA_OMADAC_ID=adbef8fa3505fb16b09818eab71d824e
|
|
OMADA_CLIENT_ID=REPLACE_OPENAPI_CLIENT_ID
|
|
OMADA_CLIENT_SECRET=REPLACE_OPENAPI_CLIENT_SECRET
|
|
OMADA_SITE_ID=REPLACE_SITE_ID
|
|
OMADA_STRICT_SSL=false
|