Files
bikoret/deploy/k8s/gitea-mcp-deployment.yaml
T
Scott KarpandClaude Opus 4.6 324cf1a2ed Fix gitea-mcp env: use GITEA_ACCESS_TOKEN, not GITEA_TOKEN
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 <noreply@anthropic.com>
2026-04-20 12:42:07 -04:00

82 lines
2.0 KiB
YAML

# Gitea MCP Server — public connector for claude.ai
#
# Deploys the official Gitea MCP server (gitea.com/gitea/gitea-mcp)
# in HTTP mode, exposing /mcp endpoint for Streamable HTTP transport.
#
# The MCP server connects to the Gitea backend at 185.19.29.94
# using a Personal Access Token stored in gitea-mcp-secrets.
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: gitea-mcp
namespace: shorashim
labels:
app.kubernetes.io/name: gitea-mcp
spec:
replicas: 1
selector:
matchLabels:
app.kubernetes.io/name: gitea-mcp
template:
metadata:
labels:
app.kubernetes.io/name: gitea-mcp
spec:
containers:
- name: gitea-mcp
image: gitea/gitea-mcp-server:latest
command: ["/app/gitea-mcp"]
args:
- "-t"
- "http"
- "--host"
- "http://185.19.29.94"
- "--port"
- "8080"
env:
- 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
resources:
requests:
memory: "64Mi"
cpu: "50m"
limits:
memory: "256Mi"
cpu: "250m"
livenessProbe:
tcpSocket:
port: 8080
initialDelaySeconds: 10
periodSeconds: 30
readinessProbe:
tcpSocket:
port: 8080
initialDelaySeconds: 5
periodSeconds: 10
---
apiVersion: v1
kind: Service
metadata:
name: gitea-mcp
namespace: shorashim
labels:
app.kubernetes.io/name: gitea-mcp
spec:
type: ClusterIP
selector:
app.kubernetes.io/name: gitea-mcp
ports:
- port: 8080
targetPort: 8080
protocol: TCP
name: http