Loading
SonicWall MCP
Power your agent
Add this server
The publisher's own command. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
Local command
mcpb https://github.com/Servosity/msp-skills/releases/download/sonicwall-v0.1.4/sonicwall-mcp.mcpbCredentials from the publisher
- SONICWALL_MSW_API_KEY — Your MySonicWall API key, sent as X-API-KEY. nsm-login (CLI or the nsm_login tool) mints the NSM session token from it, and licence and blind-spots checks read MySonicWall with it. Use an account whose NSM role is read-only.
- SONICWALL_NSM_TOKEN — Optional override; leave blank. Run `sonicwall-cli nsm-login` (or the nsm_login tool) instead, which saves the token. A pasted token expires after 8 hours (15 minutes idle) and keeps overriding the saved one.
- SONICWALL_REGION — NSM SaaS region in https://nsm-{region}.sonicwall.com: uswest (default) or eucentral for EU portals.
- SONICWALL_BASE_URL — Optional; leave blank. Sends every NSM and MySonicWall call to this base URL instead, for tests and mock servers.
- SONICWALL_MCP_READ_ONLY — Optional. Set to 1 to hide tools that change NSM, MySonicWall or firewall state and refuse non-GET execute calls. Tools still write local state: the response cache, posture snapshots and learning entries.
- SONICWALL_NO_LOCAL_DATA — Optional. Set to 1 to keep no local copy of API responses: reads go to the API and the response cache is off.
- SONICWALL_MCP_HTTP_TOKEN — Required only when running the MCP server with --transport http (a remote/hosted deployment); callers must send a matching Authorization: Bearer header. Leave blank for Claude Desktop.
- SONICWALL_USER_AGENT — Optional. Overrides the User-Agent the CLI sends to NSM and MySonicWall. Leave blank to use the built-in one.
- PRINTING_PRESS_CLIENT_PROFILE — Only used when the MCP server is bound to a tenant-gated client profile. This connector registers no tenant-gated source, so leave it blank.
Claude Code has no install link for a local command. Copy the command below and run it in a terminal.
shClaude Code
SONICWALL_MSW_API_KEY=<secret> SONICWALL_NSM_TOKEN=<secret> SONICWALL_REGION=<value> SONICWALL_BASE_URL=<value> SONICWALL_MCP_READ_ONLY=<value> SONICWALL_NO_LOCAL_DATA=<value> SONICWALL_MCP_HTTP_TOKEN=<secret> SONICWALL_USER_AGENT=<value> PRINTING_PRESS_CLIENT_PROFILE=<secret> claude mcp add io.github.servosity-sonicwall-mcp -- mcpb https://github.com/Servosity/msp-skills/releases/download/sonicwall-v0.1.4/sonicwall-mcp.mcpbRun in a terminal.
jsonClaude Desktop
{ "mcpServers": { "io.github.servosity-sonicwall-mcp": { "command": "mcpb", "args": [ "https://github.com/Servosity/msp-skills/releases/download/sonicwall-v0.1.4/sonicwall-mcp.mcpb" ], "env": { "SONICWALL_MSW_API_KEY": "<secret>", "SONICWALL_NSM_TOKEN": "<secret>", "SONICWALL_REGION": "<value>", "SONICWALL_BASE_URL": "<value>", "SONICWALL_MCP_READ_ONLY": "<value>", "SONICWALL_NO_LOCAL_DATA": "<value>", "SONICWALL_MCP_HTTP_TOKEN": "<secret>", "SONICWALL_USER_AGENT": "<value>", "PRINTING_PRESS_CLIENT_PROFILE": "<secret>" } } }}claude_desktop_config.json
Local · mcpbPublisher installStep-by-step: add this in Claude
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
Host a copy with our keys and logs.
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchServer facts
LocalTools
Tools
No tool list yet. Remote servers get one after the first health check.
FAQ