Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Audit every client FortiGate for firmware, SSL-VPN exposure, admin accounts and license expiry.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
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_PROFILEValues marked secret are keys to your account. Never share them or paste them into a chat.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
Fill in the empty values before running it.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
FORTINET_DEVICES envFORTINET_FMG_URL envFORTINET_CLOUD_API_USER envFORTINET_CLOUD_REGION envFORTINET_CLOUD_ACCOUNT_ID envFORTINET_MCP_READ_ONLY envFORTINET_USER_AGENT envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account servosity, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: FORTINET_BASE_URL, FORTINET_API_TOKEN, FORTINET_FMG_API_KEY, FORTINET_CLOUD_API_PASSWORD, FORTINET_MCP_HTTP_TOKEN, PRINTING_PRESS_CLIENT_PROFILE
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.4) reached the registry 14 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, FlyDocs
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Unofficial. Community-built Claude Code Skill and MCP server for the Fortinet
API. Not affiliated with, endorsed by, or sponsored by Fortinet, Inc.
Full skill page - install, outcomes, safety model.
Read every FortiGate's configuration and live state, then audit the whole client fleet for firmware, SSL-VPN exposure, admin accounts and license expiry in one command. Works with the AI you already use - ChatGPT (desktop app), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Gemini CLI. Free, open source, runs on your laptop. Built for MSP owners. No code required.
Security note (until this connector is reprinted). Do not run HTTP mode
(
--transport http), not even on localhost. This build checks a token, but it
predates the fix release's request size and time limits. The MCP tools can
also read your data with your credentials. Use the default stdio transport. If
you set up a tunnel for a remote agent, shut it down. A fix is on the way.
The six agents MSP owners actually use (self-serve, works today):
| Your AI agent | How to install the Fortinet skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register fortinet-mcp (no JSON editing). |
| ChatGPT (desktop app) | Run installer, then add fortinet-mcp in Settings > MCP servers as a local (STDIO) server. ChatGPT on the web is not supported yet. |
| Codex CLI | Paste the install prompt below. |
| Claude Code | Paste the install prompt below. |
| Claude Cowork | Paste the install prompt below. |
| GitHub Copilot (VS Code) | Run installer, add fortinet-mcp to mcp.json under the servers key, then pick Agent mode. |
The ChatGPT desktop app runs fortinet-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote (HTTP) server, and this connector's HTTP mode is paused until it is reprinted (see the security note in mcp-install.md), so msp-skills does not support it yet. If your team works there, a hosted gateway is the better pick; check that your AI app is on the gateway's setup list.
Big install base, but an honest heads-up: Gemini CLI runs the local binary you just installed, while Microsoft 365 Copilot and the Gemini app need a remote server, which msp-skills does not support yet.
| Agent | What it takes |
|---|---|
| Microsoft 365 Copilot / Copilot Studio | Not supported by msp-skills yet: it needs a remote server. A hosted gateway is the better pick; check that your AI app is on the gateway's setup list. |
| Google Gemini | Gemini CLI is local - same as Claude Code. See mcp-install.md. The Gemini app needs a remote server and is not supported by msp-skills yet. |
Skill-native agents (also covered): Hermes and OpenClaw read this skill's
SKILL.mddirectly *and* speak MCP - see their install sections below. Also works with Cursor, Windsurf, Cline, Continue.dev, and Zed via MCP. Full per-tool wire-up: [docs/which-agent.md](../../docs/which-agent.md).
Run more than one agent? Install across all 51+ supported agents in one command:
npx skills add Servosity/msp-skills@latest(requires Node.js, then run the per-skill installer for the CLI/MCP binaries). See docs/which-agent.md.
.mcpbDownload Fortinet MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Fortinet release on the releases page.)
Prefer the Claude Code plugin? Add the marketplace once, then install - works immediately, no directory listing required:
/plugin marketplace add Servosity/msp-skills
/plugin install fortinet@msp-skills
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the Fortinet Skill and MCP server from Servosity/msp-skills in this agent workspace. If this workspace uses a POSIX shell (macOS, Linux, WSL, or Bash), run
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/fortinet/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/fortinet/install.ps1 | iex. Then authenticate per the README and runfortinet-cli --helpto explore.
The same prompt works in any agent that can run shell.
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/fortinet/install.ps1 | iex
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/fortinet/install.sh)
The installer drops both fortinet-cli (the CLI) and fortinet-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
fortinet-cli --version
The installer always fetches the current release - re-run it to upgrade:
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/fortinet/install.sh)
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/fortinet/install.ps1 | iex
Claude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update fortinet@msp-skills.
After the installer runs, see [mcp-install.md](./mcp-install.md) and [docs/which-agent.md](../../docs/which-agent.md) for the per-agent wire-up - one section per agent, including the GitHub Copilot servers key and the ChatGPT desktop app. Claude Desktop's Settings > Extensions panel is the simplest path; the MCP config block (for users who prefer editing JSON) is documented in mcp-install.md.
From the Hermes CLI:
hermes skills install servosity/msp-skills/skills/fortinet --force
Inside a Hermes chat session:
/skills install servosity/msp-skills/skills/fortinet --force
Hermes speaks MCP natively, so it can also use the fortinet-mcp server directly - same install path, same env vars.
Tell your OpenClaw agent (copy this):
Install the fortinet skill from https://github.com/servosity/msp-skills/tree/main/skills/fortinet. The skill defines how its required CLI (
fortinet-cli) can be installed via theopenclaw:frontmatter block.
OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.
Create a REST API admin on the FortiGate (System > Administrators > Create New > REST API Admin, read-only profile, your IP as a trusted host), then:
FORTINET_BASE_URL=<value> FORTINET_API_TOKEN=<value> fortinet-cli doctor
doctor checks config and paths, then makes one authenticated read (GET /monitor/system/status) so it reports whether the token actually works, not just whether one is set. For a fleet of FortiGates, list them in a devices.toml file and run fortinet-cli fleet devices to see which entries have a usable URL and token file.
| Question your MSP keeps asking | Command |
|---|---|
| One posture verdict across every client FortiGate, only findings new since the last run | fortinet-cli fleet audit --new |
| Which FortiGates are below the fixed firmware for their branch? | fortinet-cli audit firmware --min-version 7.2.10,7.4.5 |
| Where is SSL-VPN on a WAN interface and open to any source? | fortinet-cli audit sslvpn |
| Which admins have no trusted hosts or no two-factor? | fortinet-cli audit admins |
| Which FortiGuard and FortiCare licenses expire in the next 60 days? | fortinet-cli audit licenses --within 60d |
| Which firewalls have HA out of sync, tunnels down, or certificates expiring? | fortinet-cli fleet health --cert-within 14d |
| Which policies are any-any accept, unused, or not logging? | fortinet-cli policies hygiene --unused-days 90 |
| What changed in each client's configuration this week? | fortinet-cli fleet changes --since 7d |
| Which FortiManager-managed devices are out of sync? | fortinet-cli fmg devices |
| Which FortiGate Cloud devices have the tunnel down or a contract ending? | fortinet-cli cloud devices |
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
alpadalar/fortigate-mcp-server is a general-purpose FortiGate MCP server: a device registry, read tools, and create, update and delete tools for policies, VIPs and routes that stay off unless you enable writes. It answers about the device you ask about.
This one is read-only by construction and built for the question an MSP asks the morning an SSL-VPN advisory lands: which of my 40 clients are exposed right now? A devices.toml file lists every client FortiGate, and fleet audit reads all of them in parallel, then grades each one PASS, WARN, FAIL or UNKNOWN for firmware floors per branch, SSL-VPN exposure, admin accounts and license expiry. A box it could not read is UNKNOWN, never PASS. Every run is recorded locally, so fleet audit --new shows only findings that are new since the last one, and fleet backup plus fleet changes show which configuration objects moved between two backups. fmg and cloud add the FortiManager and FortiGate Cloud inventory alongside, also read-only. Stored secrets stay out of the answers: every FortiOS-encrypted value comes back as ENC (redacted).
Fortinet's FortiAI-Assist runs inside FortiManager and FortiAnalyzer, and since FortiOS 8.0 on FortiGates with more than 2 GB of RAM and FortiCare Premium; it answers inside the console it runs in. This needs only a read-only REST API token per FortiGate, so it also covers the small boxes FortiAI-Assist does not, and it answers across every client's firewall at once.
FortiOS SSL-VPN is the part of a client's network that gets attacked first. When Fortinet disclosed CVE-2024-21762 in February 2024 it said the flaw was "potentially being exploited in the wild" (Rapid7), and the advice
Only the beginning is shown; read the rest in the repo