FortiManager Code Mode MCP

Two tools, one API

This Model Context Protocol server exposes search and execute. The agent searches the API reference, then runs JavaScript inside a QuickJS WASM sandbox. API calls go through the host; credentials remain outside the sandbox.

• Search the reference. Find objects, attributes, URLs, methods and error codes.

• Call JSON-RPC. Use fortimanager.request() with FortiManager 7.4 or 7.6.

• Choose a transport. Stdio for local clients; Streamable HTTP for hosted use.

• Speak both protocol eras. Serves the 2026-07-28 protocol revision and still answers 2025-era clients, with no configuration.

• Keep credentials on the host. Optional HTTP Bearer auth and per-request X-FMG-Token passthrough.

The execute tool is marked potentially destructive in its MCP annotations, so clients can use that when deciding whether to ask for confirmation.

Related MCP server: Code Mode MCP Server

Get started

Install from npm, run the Docker image, or build from source. Every option needs a locally generated API spec; published packages and images do not include specs.

Requirements

• Node.js 22.19.0 or newer and npm. CI checks Node 22 and 24; the Docker image runs Node 24.

• FortiManager 7.4 or 7.6, an API token, and locally generated API specs.

Before building, download the Fortinet HTML reference and run npm run generate:spec. See API spec setup. The proprietary HTML and generated specs are not redistributed.

Install from npm

Releases are published to npm as fortimanager-code-mode-mcp, without API specs. The fortimanager-mcp binary loads the spec from dist/spec/fmg-api-spec-<version>.json inside the installed package, and there is no option to point it at another directory yet (a configurable spec path is a follow-up), so copy a generated spec into the installed package before starting:

npm install -g fortimanager-code-mode-mcp
mkdir -p "$(npm root -g)/fortimanager-code-mode-mcp/dist/spec"
cp src/spec/fmg-api-spec-7.6.json "$(npm root -g)/fortimanager-code-mode-mcp/dist/spec/"
FMG_HOST=https://fmg.example.com FMG_API_TOKEN=<token> fortimanager-mcp

npx fortimanager-code-mode-mcp runs the same binary from a temporary cache. It works once the spec is copied into that cached copy, but the cache is recreated on upgrades; a global install, a source build, or Docker are steadier options.

Run with Docker

The image runs the HTTP transport on port 8000 (GET /health, POST /mcp) and ships without specs. Mount a directory containing fmg-api-spec-7.6.json (or fmg-api-spec-7.4.json) at /app/dist/spec:

docker run -d --name fortimanager-mcp -p 8000:8000 \
  -e FMG_HOST=https://fmg.example.com \
  -e FMG_API_TOKEN=<token> \
  -v /path/to/spec-dir:/app/dist/spec:ro \
  ghcr.io/jmpijll/fortimanager-code-mode-mcp:latest

FMG_API_VERSION defaults to 7.6. If only fmg-api-spec-7.4.json is mounted, add -e FMG_API_VERSION=7.4 or the server exits at startup without finding its spec.

Build from source

git clone https://github.com/jmpijll/fortimanager-code-mode-mcp.git
cd fortimanager-code-mode-mcp
npm ci
cp .env.example .env
# Edit .env: FMG_HOST and FMG_API_TOKEN.
npm run generate:spec
npm run build
npm start

The shell examples use Bash. In PowerShell, use Copy-Item .env.example .env and set variables with $env:NAME = 'value'.

Configure your MCP client with node /absolute/path/to/fortimanager-code-mode-mcp/dist/index.js. Use an absolute path and supply credentials through the client's environment configuration when its working directory does not contain your .env file. See the client setup and usage guide.

For hosted use, set MCP_TRANSPORT=http. See the configuration and auth contract. Docker instructions are in docker-compose.yml.

Important: API Spec Required

Generate the Fortinet API specs locally before starting the server. The npm package and Docker image ship without them.

Example session

After discovering the operation with the search tool, use the execute tool:

var response = fortimanager.request('get', [{ url: '/sys/status' }]);
response.result[0].data;

See the usage guide for search recipes, configuration and additional call shapes.

Know the boundaries

Verification status

Local mocked tests cover the client, sandbox, tool responses and HTTP transport. The earlier live FortiManager record is separate from the current offline suite. See the setup and verification reference for the detailed historical evidence and remaining work. New verification reports should identify the server revision, client, upstream version and operations actually exercised.

Project status

Stable · v2.0.0. Generate the required API spec before starting either transport.

Privacy

The host sends API requests to the service configured for this server. Tool results and captured sandbox logs are returned to your MCP client; that client may send them to its configured model provider. Spec caches may be written locally.

Keep .env files and credentials private. Redact account identifiers, IP addresses and service data before sharing logs or verification reports. See SECURITY.md for vulnerability reporting.

Development and contribution

npm run check

check runs lint, formatting, typecheck, mocked tests and the build. See CONTRIBUTING.md for the repository layout and contribution checks, and AGENTS.md for architectural invariants. Live API tests require separate credentials and verification scope.

Documentation

• Usage and client setup

• Architecture

• Releasing

• Changelog

License and acknowledgements

MIT. Built with TypeScript, the MCP SDK and QuickJS, following the Cloudflare Code Mode pattern.