FortiGate Read-Only

Clone the repository. The Docker backend lives in docker/ and ships a custom-catalog.yaml alongside the Dockerfile.

$ git clone https://github.com/rosarion97/Fortigate-mcp-server-public.git
$ cd Fortigate-mcp-server-public/docker

The image tag must match the image: field in custom-catalog.yaml (fortigate-readonly-mcp:latest).

$ docker build -t fortigate-readonly-mcp:latest .

Three values are required: the API token, the FortiGate host, and the VDOM you want this instance to serve. Option A keeps your token in Docker's encrypted store and is recommended; Option B writes a plaintext .env for quick local testing.

$ docker mcp secret set FORTIGATE_API_TOKEN="..."
$ docker mcp secret set FORTIGATE_HOST="fw01.example.com"
$ docker mcp secret set FORTIGATE_VDOM="root"
$ docker mcp secret set FORTIGATE_VERIFY_SSL="yes"   # optional
$ docker mcp secret ls   # values are masked

With Option A, continue through Steps 4–7 below.

$ cp .env.example .env
$ chmod 600 .env   # then set FORTIGATE_API_TOKEN, FORTIGATE_HOST, FORTIGATE_VDOM

{
  "mcpServers": {
    "fortigate-readonly": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "--env-file", "/absolute/path/to/.env",
        "fortigate-readonly-mcp:latest"
      ]
    }
  }
}

Steps 4–6 are the Option A (secret store) path. Used Option B? Skip to Step 7.

$ mkdir -p ~/.docker/mcp/catalogs
$ cp custom-catalog.yaml ~/.docker/mcp/catalogs/custom.yaml

Add the entry under the single top-level registry: key in ~/.docker/mcp/registry.yaml. Don't overwrite the file if it already exists.

registry:
  fortigate-readonly:
    catalog: custom
    enabled: true

Add the gateway block to claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json). The gateway spawns the FortiGate image on demand, reads your catalog and registry, and resolves your FORTIGATE_* secrets at request time. Replace <your-username> with your macOS username (run whoami to check):

{
  "mcpServers": {
    "mcp-toolkit-gateway": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "-v", "/var/run/docker.sock:/var/run/docker.sock",
        "-v", "/Users/<your-username>/.docker/mcp:/mcp",
        "-v", "/Users/<your-username>/Library/Caches/docker-secrets-engine/engine.sock:/root/.cache/docker-secrets-engine/engine.sock",
        "docker/mcp-gateway:latest",
        "--catalog=/mcp/catalogs/custom.yaml",
        "--registry=/mcp/registry.yaml",
        "--transport=stdio"
      ]
    }
  }
}

All three bind-mounts are required: the Docker socket lets the gateway spawn the server container; ~/.docker/mcp is where it reads your catalog and registry; the docker-secrets-engine socket is the resolver Docker Desktop exposes for the secret store, without it your FORTIGATE_* URLs resolve to empty strings and the server never starts. On Linux Docker Desktop the path is ~/.docker/desktop/secrets-engine/engine.sock; find it with find ~ -name engine.sock.

Then quit and reopen the client. claude_desktop_config.json never contains FORTIGATE_API_TOKEN, the gateway resolves it from Docker's secret store at request time. As a shortcut, docker mcp client connect claude-desktop (or MCP Toolkit → Clients in Docker Desktop) writes a similar block automatically; the explicit JSON above survives Docker Desktop updates that may rewrite the auto-managed entry.

$ docker mcp server list   # fortigate-readonly → enabled
$ docker mcp tools list

Or run the image directly, it starts and waits silently on stdin (correct for an MCP stdio server). Press Ctrl+C to exit; a missing required value fails fast on stderr.

$ docker run --rm -i --env-file .env fortigate-readonly-mcp:latest

Clone the repository. The Podman backend lives in podman/.

$ git clone https://github.com/rosarion97/Fortigate-mcp-server-public.git
$ cd Fortigate-mcp-server-public

On macOS / Windows, start a Podman machine first (podman machine init && podman machine start); Linux runs natively.

$ podman build -t fortigate-readonly-mcp:latest podman/

Three required values: FORTIGATE_API_TOKEN, FORTIGATE_HOST, and FORTIGATE_VDOM (one container serves one VDOM, use root if VDOMs are disabled). Set them in podman/.env; the file is gitignored and chmod 600'd.

$ cp podman/.env.example podman/.env
$ chmod 600 podman/.env   # then edit: FORTIGATE_API_TOKEN, FORTIGATE_HOST, FORTIGATE_VDOM

If the FortiGate uses a self-signed cert, also set FORTIGATE_VERIFY_SSL=no. Optional: FORTIGATE_PORT (default 443) and FORTIGATE_MAX_RESPONSE_BYTES (default 120000).

Point Claude Desktop at the container with the absolute path to podman/.env:

{
  "mcpServers": {
    "fortigate": {
      "command": "podman",
      "args": [
        "run", "--rm", "-i",
        "--env-file", "/absolute/path/to/podman/.env",
        "fortigate-readonly-mcp:latest"
      ]
    }
  }
}

Claude Code takes the same invocation:

$ claude mcp add -s user fortigate -- \
    podman run --rm -i \
    --env-file /absolute/path/to/podman/.env \
    fortigate-readonly-mcp:latest

-i is required, MCP stdio needs stdin attached, and every --env-file path must be absolute.

Run the image manually, it starts and waits silently on stdin. Press Ctrl+C to exit; a missing required value fails fast on stderr.

$ podman run --rm -i --env-file podman/.env fortigate-readonly-mcp:latest