From e0199042c1aa6597b8970afb65781e68d42ee0bb Mon Sep 17 00:00:00 2001 From: "fkrebs (via Claude)" Date: Fri, 22 May 2026 13:41:51 +0200 Subject: [PATCH] Re-enable nextcloud MCP: single_user_basic + NEXTCLOUD_VERIFY_SSL=false App-password generated via occ for fkrebs@nucli.de. Gateway patched to persist enabled flag from config.json across restarts. Co-Authored-By: Claude Sonnet 4.6 --- services/mcp-gateway.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/services/mcp-gateway.md b/services/mcp-gateway.md index 05acada..8010757 100644 --- a/services/mcp-gateway.md +++ b/services/mcp-gateway.md @@ -14,7 +14,7 @@ DinD MCP gateway on CT 104. Single OAuth-gated entry point fronting 24 MCP serve ## Server inventory (as of 2026-05-22) -26 servers configured in `mcp-gateway/config.json`. **Status: 25 healthy, 1 disabled.** +26 servers configured in `mcp-gateway/config.json`. **Status: 26 healthy, 1 disabled (nextcloud re-enabled 2026-05-22).** | Group | Server | Kind | Notes | |---|---|---|---| @@ -40,14 +40,14 @@ DinD MCP gateway on CT 104. Single OAuth-gated entry point fronting 24 MCP serve | | immich | spawn | | | | memos | spawn | uses `MEMOS_TOKEN` from `.env` | | | n8n | static | `https://n8n.nuclide.systems/mcp-server/http` | -| | nextcloud | spawn | ❌ **disabled** — SSL CERTIFICATE_VERIFY_FAILED contacting `https://nc.nuclide.systems` (self-signed). `"enabled": false` set 2026-05-21. | +| | nextcloud | spawn | `ghcr.io/cbcoutinho/nextcloud-mcp-server` — `single_user_basic` mode, `NEXTCLOUD_VERIFY_SSL=false`; app-password generated via `occ` for `fkrebs@nucli.de` 2026-05-22 | | | unifi | spawn | | | **image** | comfyui | static | `comfyui-mcp:8000` (own stack, see [comfyui.md](comfyui.md)) | | **storage** | upload-artifact | static | `upload-artifact-mcp:8000` | > **Catalog bridge env var passthrough**: `mcp-proxy`'s `stdio_client` uses a sanitized env (`get_default_environment()`), stripping custom vars. For catalog servers that need env vars (e.g. `gitlab`), the bridge command **must** include `--pass-environment` so Docker CLI can resolve `-e KEY` passthrough from the bridge container's env. -> **Re-enabling nextcloud**: needs either (a) a CA bundle in the container that trusts the Zoraxy/internal cert chain, or (b) skip-verify env var passed to the upstream client, or (c) point `NEXTCLOUD_HOST` at the internal Nextcloud LAN URL on `ai-internal`. Tracked as an open issue. +> **Nextcloud server count**: 27 total (26 enabled + nextcloud now re-enabled 2026-05-22). Gateway updated to persist `enabled` flag across restarts. ## Client registration