Fortinet MCP Server

A complete Model Context Protocol (MCP) server for Fortinet FortiOS 7.6.x — exposing the entire REST API (1536 endpoints) as typed MCP tools usable from Claude Desktop, Cursor, or any MCP-compatible client.. The fortinet mcp server wraps that behind the Model Context Protocol, so an assistant can use it rather than through you.

What it actually does

• 204+ typed MCP tools — organized by functional area (system, firewall, VPN, router, user, monitor, log, security, wireless)
• 5 generic pass-through tools — that cover all 1,536 FortiOS API endpoints
• Async HTTP client with Bearer-token authentication via httpx
• Full support for CMDB, Monitor, Log, and Service API sections
• Configurable SSL verification (self-signed certificates supported)
• Compatible with multi-VDOM environments

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration

You will need 4 environment variables: FORTIOS_HOST, FORTIOS_API_TOKEN, FORTIOS_VDOM, FORTIOS_VERIFY_SSL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

| Requirement | Version | |-------------|---------| | Python | 3.11+ | | Package manager | uv (recommended) or pip | | FortiGate | FortiOS 7.6.x | | Auth | REST API admin account with Bearer token | ---

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the fortinet mcp server does with a few real requests.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by paoloamato2; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.