SonicWall MCP

SonicWall + AI - for Claude, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, and any agent that speaks MCP

Unofficial. Community-built Claude Code Skill and MCP server for the SonicWall

API. Not affiliated with, endorsed by, or sponsored by SonicWall Inc.

▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.

Cyber-insurance posture for a whole SonicWall fleet: firmware, advisories, MFA, SSL-VPN exposure and licences, one row per firewall. 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.

Works with your agent

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 make changes 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):

The ChatGPT desktop app runs sonicwall-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.

Also for the Microsoft and Google stacks

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.

Skill-native agents (also covered): Hermes and OpenClaw read this skill's SKILL.md directly *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.

Install in 60 seconds

Fastest for Claude Desktop - one-click .mcpb

Download SonicWall MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every SonicWall 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 sonicwall@msp-skills

Path A - paste one prompt into your AI agent (recommended)

Copy this into Claude Code, Codex CLI, or Claude Cowork:

Install the SonicWall 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/sonicwall/install.sh). If it uses Windows PowerShell, run iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/sonicwall/install.ps1 | iex. Then authenticate per the README and run sonicwall-cli --help to explore.

The same prompt works in any agent that can run shell.

Path B - run the installer yourself

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/sonicwall/install.ps1 | iex

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/sonicwall/install.sh)

The installer drops both sonicwall-cli (the CLI) and sonicwall-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.

Verify:

sonicwall-cli --version

Upgrade to the latest 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/sonicwall/install.sh)

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/sonicwall/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 sonicwall@msp-skills.

Add to Claude Desktop, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, or another MCP client

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.

Install for Hermes

From the Hermes CLI:

hermes skills install servosity/msp-skills/skills/sonicwall --force

Inside a Hermes chat session:

/skills install servosity/msp-skills/skills/sonicwall --force

Hermes speaks MCP natively, so it can also use the sonicwall-mcp server directly - same install path, same env vars.

Install for OpenClaw

Tell your OpenClaw agent (copy this):

Install the sonicwall skill from https://github.com/servosity/msp-skills/tree/main/skills/sonicwall. The skill defines how its required CLI (sonicwall-cli) can be installed via the openclaw: frontmatter block.

OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.

Authenticate

Create a MySonicWall API key (ideally for an account whose NSM role is read-only), then mint the NSM session token from it and check it:

export SONICWALL_MSW_API_KEY=<your MySonicWall API key>

export SONICWALL_REGION=eucentral # EU NSM portals only; the default is uswest sonicwall-cli nsm-login sonicwall-cli doctor

nsm-login trades the key for an NSM session token and saves it (never printed). The token lasts 8 hours with a 15-minute idle timeout, so run nsm-login again whenever NSM commands exit 4. doctor then makes one authenticated NSM read (GET /tenants), so it reports whether the token actually works, not just whether one is set. Licence checks and blind-spots also read MySonicWall with the same key.

What this skill does

Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.

What makes this different

GTalksTech/sonicwall-mcp is a read-only Python MCP server for NSM SaaS with 46 tools for inventory, firmware, advisories, licence posture, per-site SSL-VPN configuration and config history.

This one is a single binary that works as a CLI and an MCP server, built for the questions an MSP gets the morning a SonicWall advisory lands and again at insurance renewal. posture reads every firewall in your NSM tenant through NSM's SonicOS passthrough and grades each one pass, warn, fail or unknown for firmware, end of support, advisories, licence expiry, admin TOTP and SSL-VPN exposure. mfa-audit names every local SSL-VPN user without a one-time password, blind-spots finds firewalls registered in MySonicWall that NSM cannot see, and each posture run is saved locally so posture changes shows what got worse since last week. A firewall it could not read is unknown, never pass. Secret fields SonicWall's own API schemas document (local-user and device passwords, registration and authentication codes, SNMP community names, MySonicWall API keys) are blanked before anything is printed, cached or handed to an agent.

SonicWall's SAMI is an assistant inside SonicWall's Unified Management console that answers fleet questions and can run tasks such as firmware upgrades. This works from the AI agent you already use, never changes a firewall, and grades the posture an insurer asks about per firewall.

The pain this closes

From July 2025 Akira ransomware operators went after SonicWall SSL-VPN accounts (BleepingComputer). SonicWall linked the wave to CVE-2024-40766 a