fix: add ca-certificates to bitwarden Dockerfile (curl needs HTTPS certs)

Switch from apt-get install nodejs npm to NodeSource setup_22.x
to avoid pulling 245MB of unnecessary build dependencies on
python:3.12-slim (Debian Trixie).

README.md

@@ -42,3 +42,4 @@ See each MCP's `README.md` for specific environment variables and tools.
 These MCPs run natively or are remote endpoints (no Docker image):
 
 - **playwright/** — Browser automation, runs better natively (needs display + browser)
+- **contextforge/** — Remote SSE gateway, no server to run locally

contextforge/README.md

@@ -0,0 +1,37 @@
+# contextforge-mcp
+
+MCP server gateway connecting to ContextForge backend agents. This is a remote SSE endpoint — no Docker image needed.
+
+Source: Self-hosted at `mcp-gateway.corentic.eu`
+
+## Configuration
+
+This MCP is a remote endpoint, not a local server. Configure in your AI client:
+
+```json
+{
+  "mcpServers": {
+    "contextforge": {
+      "type": "remote",
+      "url": "https://mcp-gateway.corentic.eu/sse",
+      "headers": {
+        "Authorization": "Bearer your_token",
+        "X-Forgejo-Token": "your_forgejo_token"
+      }
+    }
+  }
+}
+```
+
+## Environment Variables (for local config)
+
+Configure these in your environment:
+
+| Variable | Description |
+|----------|-------------|
+| `CONTEXTFORGE_BEARER_TOKEN` | JWT token for API auth |
+| `CONTEXTFORGE_FORGEJO_TOKEN` | Forgejo API token for repo operations |
+
+## Tools
+
+Dynamically registered by backend agents. Run `get_prompts` and `get_resources` after connecting to discover available capabilities.