x=hub

your toolset

    build deployment
    sign in

    UniFi Gateway

    mcpother
    io.github.pete-builds/unifi · v0.25.0
    deploy just this

    Safe-by-default UniFi MCP: Network + Protect + Access, multi-site, dry-run, audit log.

    run it

    on your own machines, one way per deploy method
    generated from the record, not tested yet
    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.
    #!/usr/bin/env bash
# unifi (io.github.pete-builds/unifi), recipe docker (generated).
# Generated by Hub for toolset "my-agent"; started by mcp-my-agent-unifi.service.
set -euo pipefail
export HOST=127.0.0.1 PORT=8101
exec docker run --rm --name mcp-my-agent-unifi -p 127.0.0.1:${PORT}:8000 --env-file /etc/mcp/my-agent.env ghcr.io/pete-builds/mcp-unifi:0.25.0

[Unit]
Description=MCP server unifi (toolset my-agent), generated by Hub
After=network-online.target docker.service
Wants=network-online.target

[Service]
Type=simple
User=mcp
Group=mcp
SupplementaryGroups=docker
EnvironmentFile=/etc/mcp/my-agent.env
Environment=HOME=/var/lib/mcp/unifi
WorkingDirectory=/var/lib/mcp/unifi
ExecStart=/opt/mcp/my-agent/bin/unifi.sh
Restart=on-failure
RestartSec=5
NoNewPrivileges=true
ProtectSystem=strict
ProtectHome=true
PrivateTmp=true
ReadWritePaths=/var/lib/mcp/unifi

[Install]
WantedBy=multi-user.target
    generated from the record, not tested yet
    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.
    docker run --rm -p 127.0.0.1:8101:8000 -e STUB_MODE -e UNIFI_HOST -e UNIFI_API_KEY -e UNIFI_SITE -e UNIFI_VERIFY_SSL -e MCP_UNIFI_CONTROLLERS_FILE -e MCP_UNIFI_MODULES_ENABLED -e UNIFI_ACCESS_HOST -e UNIFI_ACCESS_API_KEY -e UNIFI_ACCESS_PORT -e MCP_UNIFI_AUDIT_SINK -e MCP_UNIFI_AUDIT_PATH ghcr.io/pete-builds/mcp-unifi:0.25.0
    generated from the record, not tested yet
    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.
    # Generated by Hub for toolset "my-agent" (2026-10-18T12:17:06+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:
  unifi:
    image: ghcr.io/pete-builds/mcp-unifi:0.25.0
    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:
      STUB_MODE: ${STUB_MODE}
      UNIFI_HOST: ${UNIFI_HOST}
      UNIFI_API_KEY: ${UNIFI_API_KEY}
      UNIFI_SITE: ${UNIFI_SITE}
      UNIFI_VERIFY_SSL: ${UNIFI_VERIFY_SSL}
      MCP_UNIFI_CONTROLLERS_FILE: ${MCP_UNIFI_CONTROLLERS_FILE}
      MCP_UNIFI_MODULES_ENABLED: ${MCP_UNIFI_MODULES_ENABLED}
      UNIFI_ACCESS_HOST: ${UNIFI_ACCESS_HOST}
      UNIFI_ACCESS_API_KEY: ${UNIFI_ACCESS_API_KEY}
      UNIFI_ACCESS_PORT: ${UNIFI_ACCESS_PORT}
      MCP_UNIFI_AUDIT_SINK: ${MCP_UNIFI_AUDIT_SINK}
      MCP_UNIFI_AUDIT_PATH: ${MCP_UNIFI_AUDIT_PATH}
volumes:
  npm-cache: {}
  uv-cache: {}
    generated from the record, not tested yet
    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.
    # Generated by Hub for toolset "my-agent" (2026-10-18T12:17:06+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: unifi
  namespace: mcp
  labels: &id001
    app: unifi
spec:
  replicas: 1
  selector:
    matchLabels: *id001
  template:
    metadata:
      labels: *id001
    spec:
      containers:
      - name: unifi
        image: ghcr.io/pete-builds/mcp-unifi:0.25.0
        ports:
        - containerPort: 8000
          name: http
        env:
        - name: STUB_MODE
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: STUB_MODE
        - name: UNIFI_HOST
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: UNIFI_HOST
        - name: UNIFI_API_KEY
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: UNIFI_API_KEY
        - name: UNIFI_SITE
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: UNIFI_SITE
        - name: UNIFI_VERIFY_SSL
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: UNIFI_VERIFY_SSL
        - name: MCP_UNIFI_CONTROLLERS_FILE
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: MCP_UNIFI_CONTROLLERS_FILE
        - name: MCP_UNIFI_MODULES_ENABLED
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: MCP_UNIFI_MODULES_ENABLED
        - name: UNIFI_ACCESS_HOST
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: UNIFI_ACCESS_HOST
        - name: UNIFI_ACCESS_API_KEY
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: UNIFI_ACCESS_API_KEY
        - name: UNIFI_ACCESS_PORT
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: UNIFI_ACCESS_PORT
        - name: MCP_UNIFI_AUDIT_SINK
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: MCP_UNIFI_AUDIT_SINK
        - name: MCP_UNIFI_AUDIT_PATH
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: MCP_UNIFI_AUDIT_PATH
---
apiVersion: v1
kind: Service
metadata:
  name: unifi
  namespace: mcp
spec:
  selector:
    app: unifi
  ports:
  - port: 8000
    targetPort: http
    name: http
    generated from the record, not tested yet
    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.
    # Generated by Hub for toolset "my-agent" (2026-10-18T12:17:06+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:
  unifi:
    enabled: true
    replicas: 1
    port: 8000
    path: /mcp
    container:
      name: unifi
      image: ghcr.io/pete-builds/mcp-unifi:0.25.0
      ports:
      - containerPort: 8000
        name: http
      env:
      - name: STUB_MODE
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: STUB_MODE
      - name: UNIFI_HOST
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: UNIFI_HOST
      - name: UNIFI_API_KEY
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: UNIFI_API_KEY
      - name: UNIFI_SITE
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: UNIFI_SITE
      - name: UNIFI_VERIFY_SSL
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: UNIFI_VERIFY_SSL
      - name: MCP_UNIFI_CONTROLLERS_FILE
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: MCP_UNIFI_CONTROLLERS_FILE
      - name: MCP_UNIFI_MODULES_ENABLED
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: MCP_UNIFI_MODULES_ENABLED
      - name: UNIFI_ACCESS_HOST
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: UNIFI_ACCESS_HOST
      - name: UNIFI_ACCESS_API_KEY
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: UNIFI_ACCESS_API_KEY
      - name: UNIFI_ACCESS_PORT
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: UNIFI_ACCESS_PORT
      - name: MCP_UNIFI_AUDIT_SINK
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: MCP_UNIFI_AUDIT_SINK
      - name: MCP_UNIFI_AUDIT_PATH
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: MCP_UNIFI_AUDIT_PATH

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

    in the cloud

    one click: the provider's deploy form opens filled in, in your own account
    koyeb
    deploy to koyeb

    The form opens with CHANGE_ME for each value you supply: STUB_MODE, UNIFI_HOST, UNIFI_API_KEY, UNIFI_SITE, UNIFI_VERIFY_SSL, MCP_UNIFI_CONTROLLERS_FILE, MCP_UNIFI_MODULES_ENABLED, UNIFI_ACCESS_HOST, UNIFI_ACCESS_API_KEY, UNIFI_ACCESS_PORT, MCP_UNIFI_AUDIT_SINK, MCP_UNIFI_AUDIT_PATH. Fill them in before you deploy.

    Clients connect to the service's https://…koyeb.app address plus /mcp.

    azure
    deploy to azuretemplate

    A Container Apps environment with one app per server, each with HTTPS ingress and one replica. The portal asks for each value you supply as a secure parameter; the deployment's outputs list the endpoints.

    connect to it

    copy what your client needs
    docker run -i --rm -e STUB_MODE -e UNIFI_HOST -e UNIFI_API_KEY -e UNIFI_SITE -e UNIFI_VERIFY_SSL -e MCP_UNIFI_CONTROLLERS_FILE -e MCP_UNIFI_MODULES_ENABLED -e UNIFI_ACCESS_HOST -e UNIFI_ACCESS_API_KEY -e UNIFI_ACCESS_PORT -e MCP_UNIFI_AUDIT_SINK -e MCP_UNIFI_AUDIT_PATH ghcr.io/pete-builds/mcp-unifi:0.25.0
    {
  "mcpServers": {
    "unifi": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "STUB_MODE",
        "-e",
        "UNIFI_HOST",
        "-e",
        "UNIFI_API_KEY",
        "-e",
        "UNIFI_SITE",
        "-e",
        "UNIFI_VERIFY_SSL",
        "-e",
        "MCP_UNIFI_CONTROLLERS_FILE",
        "-e",
        "MCP_UNIFI_MODULES_ENABLED",
        "-e",
        "UNIFI_ACCESS_HOST",
        "-e",
        "UNIFI_ACCESS_API_KEY",
        "-e",
        "UNIFI_ACCESS_PORT",
        "-e",
        "MCP_UNIFI_AUDIT_SINK",
        "-e",
        "MCP_UNIFI_AUDIT_PATH",
        "ghcr.io/pete-builds/mcp-unifi:0.25.0"
      ],
      "env": {
        "STUB_MODE": "${STUB_MODE}",
        "UNIFI_HOST": "${UNIFI_HOST}",
        "UNIFI_API_KEY": "${UNIFI_API_KEY}",
        "UNIFI_SITE": "${UNIFI_SITE}",
        "UNIFI_VERIFY_SSL": "${UNIFI_VERIFY_SSL}",
        "MCP_UNIFI_CONTROLLERS_FILE": "${MCP_UNIFI_CONTROLLERS_FILE}",
        "MCP_UNIFI_MODULES_ENABLED": "${MCP_UNIFI_MODULES_ENABLED}",
        "UNIFI_ACCESS_HOST": "${UNIFI_ACCESS_HOST}",
        "UNIFI_ACCESS_API_KEY": "${UNIFI_ACCESS_API_KEY}",
        "UNIFI_ACCESS_PORT": "${UNIFI_ACCESS_PORT}",
        "MCP_UNIFI_AUDIT_SINK": "${MCP_UNIFI_AUDIT_SINK}",
        "MCP_UNIFI_AUDIT_PATH": "${MCP_UNIFI_AUDIT_PATH}"
      }
    }
  }
}
    #!/usr/bin/env bash
# Registers every server with Claude Code (run once; `claude mcp list` to check).
set -euo pipefail
set -a; [ -f .env ] && source .env; set +a
claude mcp add unifi -e "STUB_MODE=${STUB_MODE}" -e "UNIFI_HOST=${UNIFI_HOST}" -e "UNIFI_API_KEY=${UNIFI_API_KEY}" -e "UNIFI_SITE=${UNIFI_SITE}" -e "UNIFI_VERIFY_SSL=${UNIFI_VERIFY_SSL}" -e "MCP_UNIFI_CONTROLLERS_FILE=${MCP_UNIFI_CONTROLLERS_FILE}" -e "MCP_UNIFI_MODULES_ENABLED=${MCP_UNIFI_MODULES_ENABLED}" -e "UNIFI_ACCESS_HOST=${UNIFI_ACCESS_HOST}" -e "UNIFI_ACCESS_API_KEY=${UNIFI_ACCESS_API_KEY}" -e "UNIFI_ACCESS_PORT=${UNIFI_ACCESS_PORT}" -e "MCP_UNIFI_AUDIT_SINK=${MCP_UNIFI_AUDIT_SINK}" -e "MCP_UNIFI_AUDIT_PATH=${MCP_UNIFI_AUDIT_PATH}" -- docker run -i --rm -e STUB_MODE -e UNIFI_HOST -e UNIFI_API_KEY -e UNIFI_SITE -e UNIFI_VERIFY_SSL -e MCP_UNIFI_CONTROLLERS_FILE -e MCP_UNIFI_MODULES_ENABLED -e UNIFI_ACCESS_HOST -e UNIFI_ACCESS_API_KEY -e UNIFI_ACCESS_PORT -e MCP_UNIFI_AUDIT_SINK -e MCP_UNIFI_AUDIT_PATH ghcr.io/pete-builds/mcp-unifi:0.25.0

    {
  "mcpServers": {
    "unifi": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "STUB_MODE",
        "-e",
        "UNIFI_HOST",
        "-e",
        "UNIFI_API_KEY",
        "-e",
        "UNIFI_SITE",
        "-e",
        "UNIFI_VERIFY_SSL",
        "-e",
        "MCP_UNIFI_CONTROLLERS_FILE",
        "-e",
        "MCP_UNIFI_MODULES_ENABLED",
        "-e",
        "UNIFI_ACCESS_HOST",
        "-e",
        "UNIFI_ACCESS_API_KEY",
        "-e",
        "UNIFI_ACCESS_PORT",
        "-e",
        "MCP_UNIFI_AUDIT_SINK",
        "-e",
        "MCP_UNIFI_AUDIT_PATH",
        "ghcr.io/pete-builds/mcp-unifi:0.25.0"
      ],
      "env": {
        "STUB_MODE": "${STUB_MODE}",
        "UNIFI_HOST": "${UNIFI_HOST}",
        "UNIFI_API_KEY": "${UNIFI_API_KEY}",
        "UNIFI_SITE": "${UNIFI_SITE}",
        "UNIFI_VERIFY_SSL": "${UNIFI_VERIFY_SSL}",
        "MCP_UNIFI_CONTROLLERS_FILE": "${MCP_UNIFI_CONTROLLERS_FILE}",
        "MCP_UNIFI_MODULES_ENABLED": "${MCP_UNIFI_MODULES_ENABLED}",
        "UNIFI_ACCESS_HOST": "${UNIFI_ACCESS_HOST}",
        "UNIFI_ACCESS_API_KEY": "${UNIFI_ACCESS_API_KEY}",
        "UNIFI_ACCESS_PORT": "${UNIFI_ACCESS_PORT}",
        "MCP_UNIFI_AUDIT_SINK": "${MCP_UNIFI_AUDIT_SINK}",
        "MCP_UNIFI_AUDIT_PATH": "${MCP_UNIFI_AUDIT_PATH}"
      }
    }
  }
}
    {
  "servers": {
    "unifi": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "STUB_MODE",
        "-e",
        "UNIFI_HOST",
        "-e",
        "UNIFI_API_KEY",
        "-e",
        "UNIFI_SITE",
        "-e",
        "UNIFI_VERIFY_SSL",
        "-e",
        "MCP_UNIFI_CONTROLLERS_FILE",
        "-e",
        "MCP_UNIFI_MODULES_ENABLED",
        "-e",
        "UNIFI_ACCESS_HOST",
        "-e",
        "UNIFI_ACCESS_API_KEY",
        "-e",
        "UNIFI_ACCESS_PORT",
        "-e",
        "MCP_UNIFI_AUDIT_SINK",
        "-e",
        "MCP_UNIFI_AUDIT_PATH",
        "ghcr.io/pete-builds/mcp-unifi:0.25.0"
      ],
      "env": {
        "STUB_MODE": "${STUB_MODE}",
        "UNIFI_HOST": "${UNIFI_HOST}",
        "UNIFI_API_KEY": "${UNIFI_API_KEY}",
        "UNIFI_SITE": "${UNIFI_SITE}",
        "UNIFI_VERIFY_SSL": "${UNIFI_VERIFY_SSL}",
        "MCP_UNIFI_CONTROLLERS_FILE": "${MCP_UNIFI_CONTROLLERS_FILE}",
        "MCP_UNIFI_MODULES_ENABLED": "${MCP_UNIFI_MODULES_ENABLED}",
        "UNIFI_ACCESS_HOST": "${UNIFI_ACCESS_HOST}",
        "UNIFI_ACCESS_API_KEY": "${UNIFI_ACCESS_API_KEY}",
        "UNIFI_ACCESS_PORT": "${UNIFI_ACCESS_PORT}",
        "MCP_UNIFI_AUDIT_SINK": "${MCP_UNIFI_AUDIT_SINK}",
        "MCP_UNIFI_AUDIT_PATH": "${MCP_UNIFI_AUDIT_PATH}"
      }
    }
  }
}
    name: my-agent
target: local
servers:
- hub: io.github.pete-builds/unifi
    • not probed yet: tools unpinned, ingest lists them

    tools

    Not probed yetThe tools appear once the hub or its worker has listed this entry. Running it still works: your client lists them on first start.