From 70d34a348aee6eea60d5bce7c5acaa78d69e96b4 Mon Sep 17 00:00:00 2001 From: Scott Karp Date: Mon, 20 Apr 2026 12:42:07 -0400 Subject: [PATCH] Fix gitea-mcp env: use GITEA_ACCESS_TOKEN, not GITEA_TOKEN MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The gitea-mcp server expects GITEA_ACCESS_TOKEN environment variable, not GITEA_TOKEN. Without the correct env var, every API call to the backend Gitea returns "token is required" — the MCP server can't authenticate to fetch user info, repos, etc. Also added GITEA_HOST env var as a backup to the --host flag. Co-Authored-By: Claude Opus 4.6 --- deploy/k8s/gitea-mcp-deployment.yaml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/deploy/k8s/gitea-mcp-deployment.yaml b/deploy/k8s/gitea-mcp-deployment.yaml index 80ba402c..e214632a 100644 --- a/deploy/k8s/gitea-mcp-deployment.yaml +++ b/deploy/k8s/gitea-mcp-deployment.yaml @@ -35,11 +35,13 @@ spec: - "--port" - "8080" env: - - name: GITEA_TOKEN + - name: GITEA_ACCESS_TOKEN valueFrom: secretKeyRef: name: gitea-mcp-secrets key: GITEA_TOKEN + - name: GITEA_HOST + value: "http://185.19.29.94" ports: - containerPort: 8080 name: http