SSyncDev

WatchGuard MCP Server

WatchGuard Cloud Firebox, Endpoint Security, ThreatSync, NDR and AuthPoint APIs for every customer

Local serverstdio

What is the WatchGuard MCP Server?

WatchGuard MCP is an MCP integration. WatchGuard Cloud Firebox, Endpoint Security, ThreatSync, NDR and AuthPoint APIs for every customer.

Packages and local setup

The published mcpb package is https://github.com/Servosity/msp-skills/releases/download/watchguard-v0.1.9/watchguard-mcp.mcpb, version 0.1.9. Its declared MCP transport is stdio.

The package declares WATCHGUARD_CLIENT_ID (required): WatchGuard Cloud API Access ID (read-write or read-only).; WATCHGUARD_CLIENT_SECRET (required): Password for that Access ID.; WATCHGUARD_API_KEY (required): WatchGuard Cloud API key (WatchGuard-API-Key header).; WATCHGUARD_ACCOUNT_ID (required): Your WatchGuard Cloud account ID (ACC-... or WGC-...).; WATCHGUARD_BASE_URL: Optional: region API base URL; default https://api.usa.cloud.watchguard.com (EMEA api.deu, APAC api.jpn).; WATCHGUARD_TOKEN_URL: Optional: region OAuth token URL; default https://api.usa.cloud.watchguard.com/oauth/token.; WATCHGUARD_AUDIENCE: Optional: a managed account's audience value; requests use that customer's token (not a security boundary).; WATCHGUARD_OAUTH_SCOPE: Optional: OAuth scope to request; default api-access.; WATCHGUARD_USER_AGENT: Optional: override the User-Agent the CLI sends.; WATCHGUARD_MCP_READ_ONLY: Optional: set to 1 to run the MCP server read-only.; WATCHGUARD_MCP_HTTP_TOKEN: Bearer token callers must present when the server runs with --transport http; not used by the stdio transport.; WATCHGUARD_NO_LOCAL_DATA: Optional: set to 1 to turn off the response cache and local store (reads go to the API).; PRINTING_PRESS_CLIENT_PROFILE: Not enforced by this connector (no tenant-gated profiles); leave unset. It does not limit which accounts a call can reach..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.1.9 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
WATCHGUARD_CLIENT_IDWatchGuard Cloud API Access ID (read-write or read-only).Yes
WATCHGUARD_CLIENT_SECRETPassword for that Access ID.Yes
WATCHGUARD_API_KEYWatchGuard Cloud API key (WatchGuard-API-Key header).Yes
WATCHGUARD_ACCOUNT_IDYour WatchGuard Cloud account ID (ACC-... or WGC-...).Yes
WATCHGUARD_BASE_URLOptional: region API base URL; default https://api.usa.cloud.watchguard.com (EMEA api.deu, APAC api.jpn).Check documentation
WATCHGUARD_TOKEN_URLOptional: region OAuth token URL; default https://api.usa.cloud.watchguard.com/oauth/token.Check documentation
WATCHGUARD_AUDIENCEOptional: a managed account's audience value; requests use that customer's token (not a security boundary).Check documentation
WATCHGUARD_OAUTH_SCOPEOptional: OAuth scope to request; default api-access.Check documentation
WATCHGUARD_USER_AGENTOptional: override the User-Agent the CLI sends.Check documentation
WATCHGUARD_MCP_READ_ONLYOptional: set to 1 to run the MCP server read-only.Check documentation
WATCHGUARD_MCP_HTTP_TOKENBearer token callers must present when the server runs with --transport http; not used by the stdio transport.Check documentation
WATCHGUARD_NO_LOCAL_DATAOptional: set to 1 to turn off the response cache and local store (reads go to the API).Check documentation
PRINTING_PRESS_CLIENT_PROFILENot enforced by this connector (no tenant-gated profiles); leave unset. It does not limit which accounts a call can reach.Check documentation