Fix argocd MCP server transport

This commit is contained in:
2026-06-01 15:40:35 +01:00
parent 760acb67dd
commit 3c90d4d4d2
2 changed files with 7 additions and 10 deletions
@@ -4,20 +4,17 @@ metadata:
name: argocd-mcp
namespace: toolhive-system
spec:
# argoproj-labs MCP server for Argo CD. The image entrypoint already launches
# the server (default stdio transport); ToolHive proxies it to streamable-http
# at http://mcp-argocd-mcp-proxy.mcp-services:8080/mcp.
# NOTE: do NOT set args — the image ENTRYPOINT is `node` and any args replace
# the script path (e.g. "stdio" -> node stdio -> "Cannot find module /app/stdio").
# argoproj-labs MCP server for Argo CD. v0.7.0 starts streamable HTTP on
# port 3000 by default; setting args: ["stdio"] makes the image try to run
# /app/stdio and crash.
image: ghcr.io/argoproj-labs/mcp-for-argocd:v0.7.0
transport: stdio
proxyMode: streamable-http
proxyPort: 8080
transport: streamable-http
mcpPort: 3000
groupRef:
name: homelab-core
env:
- name: ARGOCD_BASE_URL
value: http://argocd-server.argocd.svc.cluster.local
value: http://argocd-server.argocd
# argocd-server serves a self-signed cert in-cluster.
- name: NODE_TLS_REJECT_UNAUTHORIZED
value: "0"