From 529e7364a9bd11bccb89c651e54af6dd2479637c Mon Sep 17 00:00:00 2001 From: NuklearRabbit <145918611+NuklearRabbit@users.noreply.github.com> Date: Wed, 5 Aug 2026 20:15:17 +0200 Subject: [PATCH] fix: pass MCP_HUB_REGISTRATION_ENABLED/MCP_HUB_BASE_URL through to the api container compose.yaml's api service environment block forwarded MCP_HUB_SERVICE_TOKEN but never these two -- so .env's value was silently ignored and Settings always fell back to its Python default (false / empty), no matter what .env said. Found while flipping the flag live: the container's actual reported registration_enabled stayed false after a full recreate, even though .env had been updated and two real mcp_tool_request audit events already existed (itworx-mcp-hub:readiness -> fleet_ops_get_operations_summary), proving the Hub's connector already reaches Fleet Ops successfully independent of this flag -- only the status display was gated, and silently stuck off. Co-Authored-By: Claude Sonnet 5 --- compose.yaml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/compose.yaml b/compose.yaml index f6883f3..7cc09c5 100644 --- a/compose.yaml +++ b/compose.yaml @@ -36,6 +36,8 @@ services: N8N_WEBHOOK_TRIGGER_TOKEN: ${MOBILITYOPS_WEBHOOK_TRIGGER_TOKEN:-replace-me-n8n-webhook-trigger-token} N8N_CALLBACK_TOKEN: ${MOBILITYOPS_CALLBACK_TOKEN:-replace-me-n8n-callback-token} MCP_HUB_SERVICE_TOKEN: ${MCP_HUB_SERVICE_TOKEN:-replace-me-mcp-hub-token} + MCP_HUB_REGISTRATION_ENABLED: ${MCP_HUB_REGISTRATION_ENABLED:-false} + MCP_HUB_BASE_URL: ${MCP_HUB_BASE_URL:-} DEMO_ORGANIZATION_NAME: ${DEMO_ORGANIZATION_NAME:-Northstar Mobility} DEMO_TIMEZONE: ${DEMO_TIMEZONE:-Europe/Brussels} DEMO_ALLOW_RESET: ${DEMO_ALLOW_RESET:-true}