ChromaDB Remote MCP Server

docker run --rm -p 127.0.0.1:8101:8000 -e CHROMADB_MCP_URL -e MCP_AUTH_TOKEN devsaurus/chromadb-remote-mcp:latest

# Generated by Hub for toolset "my-agent" (2026-10-18T02:59:31+00:00).
# Each package server runs behind a stdio->HTTP bridge and listens on localhost only.
#   cp .env.example .env    # fill the ${VAR}s
#   docker compose up -d && bash smoke.sh
# Remote servers are not here: clients reach them directly (see clients/).
name: mcp-my-agent
services:
  chromadb-remote:
    image: devsaurus/chromadb-remote-mcp:latest
    ports:
    - 127.0.0.1:8101:8000
    restart: unless-stopped
    x-note: 'CHANGE_ME: check the image''s README for its transport and port; this assumes streamable
      HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command
      instead.'
    environment:
      CHROMADB_MCP_URL: ${CHROMADB_MCP_URL}
      MCP_AUTH_TOKEN: ${MCP_AUTH_TOKEN}
volumes:
  npm-cache: {}
  uv-cache: {}

# Generated by Hub for toolset "my-agent" (2026-10-18T02:59:31+00:00).
#   kubectl create namespace mcp
#   kubectl -n mcp create secret generic mcp-credentials --from-env-file=.env
#   kubectl apply -f kubernetes.yaml
# Services are cluster-internal: <name>.mcp.svc.cluster.local:8000/mcp. Put an ingress
# with auth in front before exposing any of them.
apiVersion: v1
kind: Namespace
metadata:
  name: mcp
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: chromadb-remote
  namespace: mcp
  labels: &id001
    app: chromadb-remote
spec:
  replicas: 1
  selector:
    matchLabels: *id001
  template:
    metadata:
      labels: *id001
    spec:
      containers:
      - name: chromadb-remote
        image: devsaurus/chromadb-remote-mcp:latest
        ports:
        - containerPort: 8000
          name: http
        env:
        - name: CHROMADB_MCP_URL
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: CHROMADB_MCP_URL
        - name: MCP_AUTH_TOKEN
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: MCP_AUTH_TOKEN
---
apiVersion: v1
kind: Service
metadata:
  name: chromadb-remote
  namespace: mcp
spec:
  selector:
    app: chromadb-remote
  ports:
  - port: 8000
    targetPort: http
    name: http

# Generated by Hub for toolset "my-agent" (2026-10-18T02:59:31+00:00).
# Credentials come from the Secret 'mcp-credentials' (kubectl create secret generic ... --from-env-file=.env).
# Each server under `servers` is one Deployment + Service; the keys after it configure
# upstream charts a worker verified.
servers:
  chromadb-remote:
    enabled: true
    replicas: 1
    port: 8000
    path: /mcp
    container:
      name: chromadb-remote
      image: devsaurus/chromadb-remote-mcp:latest
      ports:
      - containerPort: 8000
        name: http
      env:
      - name: CHROMADB_MCP_URL
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: CHROMADB_MCP_URL
      - name: MCP_AUTH_TOKEN
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: MCP_AUTH_TOKEN

# helm install my-agent helm/my-agent -n mcp