SonicWall MCP

This entry doesn't list a package or endpoint. Check its source ↗ for setup steps.

• SONICWALL_MSW_API_KEYrequiredsecretYour 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
• SONICWALL_NSM_TOKENsecretOptional 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 m
• SONICWALL_REGIONNSM SaaS region in https://nsm-{region}.sonicwall.com: uswest (default) or eucentral for EU portals.
• SONICWALL_BASE_URLOptional; leave blank. Sends every NSM and MySonicWall call to this base URL instead, for tests and mock servers.
• SONICWALL_MCP_READ_ONLYOptional. 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 ca
• SONICWALL_NO_LOCAL_DATAOptional. 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_TOKENsecretRequired only when running the MCP server with --transport http (a remote/hosted deployment); callers must send a matching Authorization: Bearer header. Leave b
• SONICWALL_USER_AGENTOptional. Overrides the User-Agent the CLI sends to NSM and MySonicWall. Leave blank to use the built-in one.
• PRINTING_PRESS_CLIENT_PROFILEsecretOnly used when the MCP server is bound to a tenant-gated client profile. This connector registers no tenant-gated source, so leave it blank.