x=hub

your toolset

    build deployment
    sign in

    Fortinet MCP

    mcpother
    io.github.Servosity/fortinet-mcp · v0.1.1
    deploy just this

    Audit every client FortiGate for firmware, SSL-VPN exposure, admin accounts and license expiry.

    run it

    on your own machines, one way per deploy method
    generated from the record, not tested yet
    CHANGE_ME: built from the repository's Dockerfile, assuming it serves streamable HTTP at :8000/mcp. Nothing has run this yet; the worker replaces it with a tested recipe.
    # once, as root:
docker build -t mcp-local/fortinet:latest https://github.com/servosity/msp-skills.git#:skills/fortinet

#!/usr/bin/env bash
# fortinet (io.github.Servosity/fortinet-mcp), recipe docker (generated).
# Generated by Hub for toolset "my-agent"; started by mcp-my-agent-fortinet.service.
set -euo pipefail
export HOST=127.0.0.1 PORT=8101
exec docker run --rm --name mcp-my-agent-fortinet -p 127.0.0.1:${PORT}:8000 --env-file /etc/mcp/my-agent.env mcp-local/fortinet:latest

[Unit]
Description=MCP server fortinet (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/fortinet
WorkingDirectory=/var/lib/mcp/fortinet
ExecStart=/opt/mcp/my-agent/bin/fortinet.sh
Restart=on-failure
RestartSec=5
NoNewPrivileges=true
ProtectSystem=strict
ProtectHome=true
PrivateTmp=true
ReadWritePaths=/var/lib/mcp/fortinet

[Install]
WantedBy=multi-user.target
    generated from the record, not tested yet
    CHANGE_ME: built from the repository's Dockerfile, assuming it serves streamable HTTP at :8000/mcp. Nothing has run this yet; the worker replaces it with a tested recipe.
    docker build -t fortinet https://github.com/servosity/msp-skills.git#:skills/fortinet
docker run --rm -p 127.0.0.1:8101:8000 -e FORTINET_BASE_URL -e FORTINET_API_TOKEN -e FORTINET_DEVICES -e FORTINET_FMG_URL -e FORTINET_FMG_API_KEY -e FORTINET_CLOUD_API_USER -e FORTINET_CLOUD_API_PASSWORD -e FORTINET_CLOUD_REGION -e FORTINET_CLOUD_ACCOUNT_ID -e FORTINET_MCP_READ_ONLY -e FORTINET_MCP_HTTP_TOKEN -e FORTINET_USER_AGENT -e PRINTING_PRESS_CLIENT_PROFILE fortinet
    generated from the record, not tested yet
    CHANGE_ME: built from the repository's Dockerfile, assuming it serves streamable HTTP at :8000/mcp. Nothing has run this yet; the worker replaces it with a tested recipe.
    # Generated by Hub for toolset "my-agent" (2026-10-18T05:11:33+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:
  fortinet:
    build:
      context: https://github.com/servosity/msp-skills.git#:skills/fortinet
    ports:
    - 127.0.0.1:8101:8000
    restart: unless-stopped
    x-note: 'CHANGE_ME: built from the repository''s Dockerfile, assuming it serves streamable HTTP at
      :8000/mcp. Nothing has run this yet; the worker replaces it with a tested recipe.'
    environment:
      FORTINET_BASE_URL: ${FORTINET_BASE_URL}
      FORTINET_API_TOKEN: ${FORTINET_API_TOKEN}
      FORTINET_DEVICES: ${FORTINET_DEVICES}
      FORTINET_FMG_URL: ${FORTINET_FMG_URL}
      FORTINET_FMG_API_KEY: ${FORTINET_FMG_API_KEY}
      FORTINET_CLOUD_API_USER: ${FORTINET_CLOUD_API_USER}
      FORTINET_CLOUD_API_PASSWORD: ${FORTINET_CLOUD_API_PASSWORD}
      FORTINET_CLOUD_REGION: ${FORTINET_CLOUD_REGION}
      FORTINET_CLOUD_ACCOUNT_ID: ${FORTINET_CLOUD_ACCOUNT_ID}
      FORTINET_MCP_READ_ONLY: ${FORTINET_MCP_READ_ONLY}
      FORTINET_MCP_HTTP_TOKEN: ${FORTINET_MCP_HTTP_TOKEN}
      FORTINET_USER_AGENT: ${FORTINET_USER_AGENT}
      PRINTING_PRESS_CLIENT_PROFILE: ${PRINTING_PRESS_CLIENT_PROFILE}
volumes:
  npm-cache: {}
  uv-cache: {}
    generated from the record, not tested yet
    CHANGE_ME: built from the repository's Dockerfile, assuming it serves streamable HTTP at :8000/mcp. Nothing has run this yet; the worker replaces it with a tested recipe.
    # Generated by Hub for toolset "my-agent" (2026-10-18T05:11:33+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: fortinet
  namespace: mcp
  labels: &id001
    app: fortinet
spec:
  replicas: 1
  selector:
    matchLabels: *id001
  template:
    metadata:
      labels: *id001
    spec:
      containers:
      - name: fortinet
        image: CHANGE_ME
        ports:
        - containerPort: 8000
          name: http
        env:
        - name: FORTINET_BASE_URL
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: FORTINET_BASE_URL
        - name: FORTINET_API_TOKEN
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: FORTINET_API_TOKEN
        - name: FORTINET_DEVICES
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: FORTINET_DEVICES
        - name: FORTINET_FMG_URL
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: FORTINET_FMG_URL
        - name: FORTINET_FMG_API_KEY
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: FORTINET_FMG_API_KEY
        - name: FORTINET_CLOUD_API_USER
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: FORTINET_CLOUD_API_USER
        - name: FORTINET_CLOUD_API_PASSWORD
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: FORTINET_CLOUD_API_PASSWORD
        - name: FORTINET_CLOUD_REGION
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: FORTINET_CLOUD_REGION
        - name: FORTINET_CLOUD_ACCOUNT_ID
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: FORTINET_CLOUD_ACCOUNT_ID
        - name: FORTINET_MCP_READ_ONLY
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: FORTINET_MCP_READ_ONLY
        - name: FORTINET_MCP_HTTP_TOKEN
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: FORTINET_MCP_HTTP_TOKEN
        - name: FORTINET_USER_AGENT
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: FORTINET_USER_AGENT
        - name: PRINTING_PRESS_CLIENT_PROFILE
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: PRINTING_PRESS_CLIENT_PROFILE
---
apiVersion: v1
kind: Service
metadata:
  name: fortinet
  namespace: mcp
spec:
  selector:
    app: fortinet
  ports:
  - port: 8000
    targetPort: http
    name: http
    generated from the record, not tested yet
    CHANGE_ME: built from the repository's Dockerfile, assuming it serves streamable HTTP at :8000/mcp. Nothing has run this yet; the worker replaces it with a tested recipe.
    # Generated by Hub for toolset "my-agent" (2026-10-18T05:11:33+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:
  fortinet:
    enabled: true
    replicas: 1
    port: 8000
    path: /mcp
    container:
      name: fortinet
      image: CHANGE_ME
      ports:
      - containerPort: 8000
        name: http
      env:
      - name: FORTINET_BASE_URL
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: FORTINET_BASE_URL
      - name: FORTINET_API_TOKEN
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: FORTINET_API_TOKEN
      - name: FORTINET_DEVICES
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: FORTINET_DEVICES
      - name: FORTINET_FMG_URL
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: FORTINET_FMG_URL
      - name: FORTINET_FMG_API_KEY
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: FORTINET_FMG_API_KEY
      - name: FORTINET_CLOUD_API_USER
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: FORTINET_CLOUD_API_USER
      - name: FORTINET_CLOUD_API_PASSWORD
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: FORTINET_CLOUD_API_PASSWORD
      - name: FORTINET_CLOUD_REGION
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: FORTINET_CLOUD_REGION
      - name: FORTINET_CLOUD_ACCOUNT_ID
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: FORTINET_CLOUD_ACCOUNT_ID
      - name: FORTINET_MCP_READ_ONLY
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: FORTINET_MCP_READ_ONLY
      - name: FORTINET_MCP_HTTP_TOKEN
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: FORTINET_MCP_HTTP_TOKEN
      - name: FORTINET_USER_AGENT
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: FORTINET_USER_AGENT
      - name: PRINTING_PRESS_CLIENT_PROFILE
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: PRINTING_PRESS_CLIENT_PROFILE

# 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: FORTINET_BASE_URL, FORTINET_API_TOKEN, FORTINET_DEVICES, FORTINET_FMG_URL, FORTINET_FMG_API_KEY, FORTINET_CLOUD_API_USER, FORTINET_CLOUD_API_PASSWORD, FORTINET_CLOUD_REGION, FORTINET_CLOUD_ACCOUNT_ID, FORTINET_MCP_READ_ONLY, FORTINET_MCP_HTTP_TOKEN, FORTINET_USER_AGENT, PRINTING_PRESS_CLIENT_PROFILE. Fill them in before you deploy.

    Koyeb builds the repository's Dockerfile from branch main; change the branch in the form if the default one has another name.

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

    cloud run
    run on google cloud

    Cloud Shell clones the repository, builds its Dockerfile and deploys it to Cloud Run.

    Cloud Run sends requests to $PORT (8080); the recipe expects :8000, so the server has to read PORT, or set the container port on the service afterwards.

    Set FORTINET_BASE_URL, FORTINET_API_TOKEN, FORTINET_DEVICES, FORTINET_FMG_URL, FORTINET_FMG_API_KEY, FORTINET_CLOUD_API_USER, FORTINET_CLOUD_API_PASSWORD, FORTINET_CLOUD_REGION, FORTINET_CLOUD_ACCOUNT_ID, FORTINET_MCP_READ_ONLY, FORTINET_MCP_HTTP_TOKEN, FORTINET_USER_AGENT, PRINTING_PRESS_CLIENT_PROFILE on the service afterwards: the button asks only for what the repository's own app.json lists.

    connect to it

    copy what your client needs
    {
  "mcpServers": {
    "fortinet": {
      "command": "CHANGE_ME",
      "args": []
    }
  }
}
    #!/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 fortinet -- CHANGE_ME

    {
  "mcpServers": {
    "fortinet": {
      "command": "CHANGE_ME",
      "args": []
    }
  }
}
    {
  "servers": {
    "fortinet": {
      "type": "stdio",
      "command": "CHANGE_ME",
      "args": []
    }
  }
}
    name: my-agent
target: local
servers:
- hub: io.github.Servosity/fortinet-mcp
    • not probed yet: tools unpinned, ingest lists them
    • no recipe for target 'local': fill the files by hand

    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.