Add nodered-mcp chart (fgjcarlos/nodered-mcp)

MCP server exposing a Node-RED instance's admin API as agent tools.
Single Deployment + Service + Ingress, image tracked off the upstream
releases -- the tags are v-prefixed but the ghcr image tags are not,
hence the version-pattern.

MCP_HTTP_TOKEN is required rather than optional: upstream's listener
binds all container interfaces, so there is no loopback-trust mode. The
chart therefore requires existingSecret instead of defaulting it away.
readOnly defaults on, so an agent cannot deploy flows by accident.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

nodered-mcp/values.yaml

@@ -0,0 +1,52 @@
+image:
+  repository: ghcr.io/fgjcarlos/nodered-mcp
+  pullPolicy: IfNotPresent
+
+# The container's HTTP listener. Upstream's streamable-HTTP transport serves
+# MCP at /mcp on this port.
+port: 8090
+
+service:
+  type: ClusterIP
+  port: 8090
+
+# The Node-RED admin API this server drives, e.g. http://node-red:1880
+noderedURL: ""
+
+# Refuse every write tool (flow deploy, node install). Leave on unless the
+# agent is meant to change flows.
+readOnly: true
+
+# Secret holding the server's own bearer token. Upstream requires
+# MCP_HTTP_TOKEN — the listener binds all interfaces, so there is no
+# "trusted loopback" mode to fall back on.
+existingSecret: ""
+tokenKey: MCP_HTTP_TOKEN
+
+# Additional non-secret environment variables
+env: {}
+
+# Additional secret-backed environment variables
+secretEnvKeys: []
+  # - envName: NODERED_TOKEN
+  #   secretKey: NODERED_TOKEN
+
+resources:
+  requests:
+    cpu: "50m"
+    memory: "64Mi"
+  limits:
+    cpu: "500m"
+    memory: "256Mi"
+
+nodeSelector: {}
+tolerations: []
+affinity: {}
+
+ingresses: {}
+  # https:
+  #   host: red-mcp.mcp.example.com
+  #   annotations: {}
+  #   tls:
+  #     - hosts:
+  #         - red-mcp.mcp.example.com